This command allocates three channels for jobs on device type DISK : These commands back up to a media manager using two tape drives in parallel: Each configured sbt channel will back up roughly half the total data.
After connecting to the target database and recovery catalog (if you use one), run the SHOW EXCLUDE command. backup on that device only. LinuxMonitoringRemote supportRemote do the work either on disk or on the tape. For example, to test whether your backup goes successfully to tape, you might run the following command: The specifics of your PARMS and FORMAT settings depend on the media management software that you are using. Copyright 1996 - 2020 This Assume that you issue the following commands at the RMAN prompt: The backup of the users tablespace uses the configured sbt channel and the configured default MAXSETSIZE setting of 7500K.
The CONFIGURE MAXSETSIZE command limits the size of backup sets created on a channel. For example, the following vendor-specific PARMS setting instructs the media manager to back up to a volume pool called oracle_tapes: Refer to your third-party vendor documentation for the appropriate settings.
By default, RMAN has preconfigured a disk channel so that you can back up to disk without doing any manual configuration. The channels can be configured to You can change the number of copies done for the files by the "Manual Parallelization of Backups" for concepts, Oracle Database Backup and Recovery Reference for BACKUP syntax, Oracle Database Backup and Recovery Reference for CONFIGURE syntax, Oracle Database Backup and Recovery Reference for SET syntax. If you set the maximum set size to 2049, then RMAN rounds down this value to 2 kilobytes (2048 bytes). In this case, you can run the following commands: You can configure persistent settings for your channels, such as channel parameters, parallelism, and the default device type for backups. configure command like following: RMAN> configure Configure disk channels as follows: In this example, assume that you have two tape drives and want each tape drive to use tapes from a different tape pool. The following setup procedure references the sections in "Configuring Channels" where it is appropriate.
Verify This tablespace exclusion feature is useful when you do not want to make a specified tablespace part of the regular backup schedule, as in these cases: A tablespace is easy to rebuild, so it is more cost-effective to rebuild it than back it up every day.
run block. The configured settings are stored in the RMAN repository. which you can take a backup, disk In general, you should only need to set the snapshot control file location when you are upgrading to the current release from a release earlier than 8.1.7. or have a suggestion for improving our content, we would appreciate your Subsequent snapshot control files that RMAN creates use the specified filename. Configuring Datafile and Archive Log File Copies. On UNIX, the default library filename is $ORACLE_HOME/lib/libobk.so, with the extension name varying according to platform: .so, .sl, .a, and so forth. UpgradesSQL For example, enter: Start SQL*Plus and then connect using both the shared server and dedicated server service names to confirm the mode of each session. If you have a flash recovery area configured, you can explicitly add the flash recovery area to the set of archiving destinations by setting one of the LOG_ARCHIVE_DEST_n parameters to LOCATION=USE_DB_RECOVERY_FILE_DEST (note that this does not have to be LOG_ARCHIVE_DEST_10). BACKUP COPIES is set to 1 for each device type. Consulting StaffConsulting To work with restrictions on file names and sizes imposed by your media manager, you may need to configure RMAN settings that control the naming and size of backup pieces. If you set any local destinations for LOG_ARCHIVE_DEST_n, then archived redo logs are stored only in the destinations you specify using those parameters. For any other errors, check the trace file in USER_DUMP_DEST directory for more information. Full details on the backup optimization algorithm are provided in "Backup Optimization". Oracle If you configure settings for a specific channel using CONFIGURE CHANNEL with a channel number, RMAN uses those specified configured settings. In this case, redo log files are not archived in the flash recovery area by default. If you do not specify the FORMAT parameter, then RMAN automatically generates a unique filename with the %U substitution variable. Possible failures include the following cases: Ensure that the steps in "Configuring RMAN to Make Backups to a Media Manager" are correctly done. If you find an error strive to update our BC Oracle support information. RMAN needs a snapshot control file only when resynchronizing with the recovery catalog or when making a backup of the current control file. Note that you can specify the FORMAT string on the BACKUP, CONFIGURE CHANNEL, and ALLOCATE CHANNEL commands. A tablespace contains temporary or test data that you do not need to back up. For example, assume that the default device type is configured to sbt, and you execute this command: In this case, RMAN uses only the disk channel that you manually allocated within the RUN block, overriding any defaults set by using CONFIGURE DEVICE TYPE, CONFIGURE DEFAULT DEVICE, or CONFIGURE CHANNEL settings. configure channel command This module contains the media management library that the Oracle database loads and uses when accessing the media manager. The default value for the snapshot control file is platform-specific and depends on the Oracle home. The snapshot control file location is not set to the default value. You can increase the number channel, you need to use the allocate channel commandwhich is a batch command and can only run within the For an overview of configured channels and how they are used, refer to the section "Configuring Channels". Configure your default output device and default sbt channels as follows: When parallelizing, RMAN always allocates channels beginning with CHANNEL 1 and ending with channel number equal to the PARALLELISM setting. For example, connect the RMAN client to the target and, if applicable, the recovery catalog. 
In this example, you want to send disk backups to two different disks. If you receive the ORA-27211 error, the media management library could not be loaded: In this case, you must check your media management installation to make sure that the library is correctly installed, and re-check the value for the SBT_LIBRARY parameter as described in "Locating the Media Management Library: The SBT_LIBRARY Parameter".
Instead, RMAN uses the snapshot location that is already stored in the control file. RMAN always allocates the number of channels specified in PARALLELISM, using specifically configured channels if you have configured them and generic channels if you have not. The difference is that after you set the AUXNAME the first time, you do not need to reset the filename when you issue another DUPLICATE command: the AUXNAME setting remains in effect until you issue CONFIGURE AUXNAME CLEAR.
You can use the substitution variables provided by RMAN to generate unique backup piece names. advertisements and self-proclaimed expertise. You can override the configured MAXSETSIZE value by specifying a MAXSETSIZE option for an individual BACKUP command. If you choose to use RMAN with a media manager, then you must obtain all product-specific information from the vendor. When allocating or configuring channels for RMAN to use to communicate with a media manager, specify the SBT_LIBRARY parameter to provide the path to the media management software library. When renaming files with the DUPLICATE command, CONFIGURE AUXNAME is an alternative to SET NEWNAME. As a rule, allocating one channel for each physical device is best. Database Support You can change the preset channels with the configure This chapter describes how to perform setup and configuration tasks.
The media manager considers the backup piece name as the filename of the backup file, so this name must be unique in the media manager catalog. For example, you can run: By default, backup optimization is configured to OFF. To show the default device type for backups: After connecting to the target database and recovery catalog (if you use one), run the SHOW DEFAULT DEVICE TYPE command. By default, channel parallelism for each configured device is set to 1. Remote Depending on the type of media management software that you installed, you may have to define media pools, configure users and classes, and so forth.
If you do not provide a value for this parameter, RMAN looks in a platform-specific default location. When you use that specific numbered channel in a backup, the configured settings for that channel will be used instead of the configured generic channel settings. Oracle For example, after the second CONFIGURE CHANNEL command, which specifies only a FORMAT for configured disk channels, the MAXPIECESIZE for the disk channel is returned to its default value: You can also configure default settings for individual channels from a group of parallelized channels by specifying a channel number. After testing a channel allocation on the media manager, make a test backup. Remote DBA Services sessions that do all the work of backup, restore and recovery. If the backup succeeds, then you are ready to make backups to your media manager. and tape(SBT). RMAN> configure For example, CONFIGURE DEVICE TYPE CLEAR does not clear CONFIGURE DEFAULT DEVICE TYPE. Each CONFIGURE CLEAR command clears only itself. See Chapter 8, "RMAN Tablespace Point-in-Time Recovery (TSPITR)" for more details on using CONFIGURE AUXNAME in connection with TSPITR, and Chapter 13, "Creating and Updating Duplicate Databases with RMAN" for more on using CONFIGURE AUXNAME in performing database duplication. In contrast, you must reissue the SET NEWNAME command every time you rename files. After installing the media management software, perform whatever configuration that your vendor requires so that the software can accept RMAN backups. If you set the PARALLELISM for a device, and then make the device default, then RMAN uses the generic configured channel settings for each parallelized channel. CONFIGURE CHANNEL takes the same options used to specify one-time options with ALLOCATE CHANNEL. The exclusion condition applies to any datafiles that you add to this tablespace in the future.
You may need to manage the naming of backup pieces to be written to the media manager, so that backup pieces have unique names. The following statements can create online redo logs in the flash recovery area: The default size of an online log created in the flash recovery area is 100 MB. This section describes RMAN commands or implicit actions (such as control file autobackup) that can create files in the flash recovery area, and how to control whether a specific command creates files there or in some other destination. For example, you can configure default parameters for disk and tape channels as in this example: You can configure generic channel settings for a device type, that is, a template that is used for any channels created based on configured settings for that device. For a full description of how these parameters interact, see the "Semantics" section of the description of CREATE CONTROLFILE in Oracle Database SQL Reference. In general, you should begin by installing and configuring the media management software on the target host or production network.
RMAN requires a dedicated server process. Start RMAN and connect to the target database. Oracle Explicitly or implicitly (as in the case of), set one of the LOG_ARCHIVE_DEST_n) parameters to 'LOCATION=USE_DB_RECOVERY_FILE_DEST'. For example, if you set the maximum set size to 2000, then RMAN rounds down this value to 1 kilobyte (1024 bytes). would consume, making the performance affected as well. device type disk parallelism 4; There can be two channels linked with the type of devices on Assume you enter the following channel configuration: The following table illustrates the channel names and channel settings that RMAN allocates when the default device is DISK and PARALLELISM for DISK is set to 4. Configuring parallelism for a device type specifies the number of server sessions to be used for I/O to that device type. You can clear channel and device settings by using these commands: CONFIGURE CHANNEL n DEVICE TYPE CLEAR (where n is an integer). publish Ensure that the steps in, Create a new database in the current release. The Oracle of For example, assume that you configure BACKUP COPIES to 3. For example, enter: Sample output for SHOW DATAFILE BACKUP COPIES follows: You can run CONFIGURE EXCLUDE FOR TABLESPACE to exempt the specified tablespace from the BACKUP DATABASE command. Oracle Net configuration varies greatly from system to system. experience! Whatever archiving scheme you choose, it is always advisable to create multiple copies of archived logs. These commands restore archived redo logs from backup for use during media recovery, as required by the command. By default, the location of the snapshot control file is determined by the rules in the following table: You can see the current snapshot location by running the SHOW command. The following procedure illustrates only one method.
If you are backing up to only one disk location or only one tape drive, then you need only one channel. This feature is known as duplexing. To allocate a manual Run the CONFIGURE CHANNEL n command (where n is a positive integer less than 255) to configure a specific channel.
UNIXOracle Check if there are any media manager jobs in "tape mount request" mode and fix the problem. considering using the services of an Oracle support expert should After you have confirmed that the database server can load the media management library, test to make sure that RMAN can back up to the media manager. Oracle Database Backup and Recovery Basics, "After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario", Oracle Database Backup and Recovery Reference, "Locating the Media Management Library: The SBT_LIBRARY Parameter", "Configuring RMAN to Make Backups to a Media Manager", "Configuring Channel Settings for a Device Type", "Determining Channel Parallelism to Match Hardware Devices", Oracle Database Backup and Recovery Reference', "Automatic Channel-Specific Configurations", "Configuring Specific Channels: Examples", "Backing Up Files Using Backup Optimization", Chapter 8, "RMAN Tablespace Point-in-Time Recovery (TSPITR)", Chapter 13, "Creating and Updating Duplicate Databases with RMAN", "Backup Fails Because of Control File Enqueue: Scenario", Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide, "Setting the Snapshot Control File Location". Refer to "Backup Job Is Hanging: Scenario" if the problem persists. If the database is unable to locate a media management library in the location specified by the SBT_LIBRARY parameter or the default location, then RMAN issues an ORA-27211 error and exits.
Tips
If DB_RECOVERY_FILE_DEST is specified (that is, if a flash recovery area is configured) and no LOG_ARCHIVE_DEST_n is specified, then LOG_ARCHIVE_DEST_10 is implicitly set to the flash recovery area. For example, enter: Scripting on this page enhances content navigation, but does not change the content in any way. For example, enter: When performing tablespace point-in-time recovery (TSPITR) or duplicating a database using RMAN, you may want to set the names of datafiles in the auxiliary instance before startingthe actual TSPITR or database duplication. RMAN comes with a Then enter: Issue the SHOW DEVICE TYPE command to display the configured devices and their PARALLELISM and backup type settings. The actual steps depend on the media management product that you install and the platform on which you are running the database. If you do not set any value for LOG_ARCHIVE_DEST, LOG_ARCHIVE_DEST_n, or DB_RECOVERY_FILE_DEST, then the redo logs are archived to a default location that is platform-specific. PricesHelp to start working with RMAN immediately over the disk drive. To reset the snapshot control file location to the default, run the CONFIGURE SNAPSHOT CONTROLFILE LOCATION CLEAR command. In these earlier releases, the default location for the snapshot control file was not dependent on the Oracle home, whereas in the current release the default location is dependent on the Oracle home. To show the default device type and currently configured settings for disk and sbt devices: After connecting to the target database and recovery catalog (if you use one), run the SHOW DEVICE TYPE command. the most difficult Oracle performance and recovery issues. Note that if you have a flash recovery area configured, the default location for the snapshot control file is not the flash recovery area. You can use SHOW BACKUP OPTIMIZATION to view the current settings of backup optimization as configured with the CONFIGURE BACKUP OPTIMIZATION command. Note that backup optimization applies only to the following commands: BACKUP ARCHIVELOG with ALL or LIKE options. A hanging backup usually indicates that the media manager is waiting to mount a tape. Performance Tuning. In such a case, RMAN creates backup pieces and image copies in the flash recovery area, with names in Oracle Managed Files name format. When you issue the BACKUP command, RMAN allocates only default channels of the type set by the CONFIGURE DEFAULT DEVICE TYPE command.
Oracle For example, it may happen that you When manually numbering channels, you must specify one or more channel options (for example, MAXPIECESIZE or FORMAT) for each channel. For example, enter: Sample output for SHOW DEVICE TYPE follows: Issue the SHOW DEFAULT DEVICE TYPE command to display the settings for the default device type for backups. To limit backup piece sizes, use the parameter MAXPIECESIZE, which you can set in the CONFIGURE CHANNEL and ALLOCATE CHANNEL commands. The PARALLELISM setting is not constrained by the number of specifically configured channels. Feel free to ask questions on our For example, enter: Sample output for SHOW MAXSETSIZE follows: Run the CONFIGURE command to enable and disable backup optimization. The commands are: Do not specify a FORMAT option to the BACKUP command, and do not configure a FORMAT option for disk backups. Configure specific channels by number when it is necessary to control the parameters set for each channel separately. The interactions among different initialization parameters affecting redo log archiving distinctions are as follows: If LOG_ARCHIVE_DEST (and, optionally, LOG_ARCHIVE_DUPLEX_DEST) is set, these parameters will specify the only redo log archiving destinations. Enable archiving to the flash recovery area and set other LOG_ARCHIVE_DEST_n initialization parameter to locations outside the flash recovery area. RMAN does not change the PARALLELISM setting for the device type because PARALLELISM is specified through a separate CONFIGURE command. After connecting to the target database and recovery catalog (if you use one), issue the SHOW CHANNEL command to display the currently configured channel settings. The channelfor which device it is configured for would take the The channel allocation can be manual or automatic. Scripts
Control file autobackups will be placed in the flash recovery area when no other destination is configured. You can always override configured channels with ALLOCATE CHANNEL for a particular backup job surrounded by a RUN block. BACKUP COPIES, Configuring Tablespaces for Exclusion from Whole Database Backups, Setting the Snapshot Control File Location, Setting Up RMAN for Use with a Shared Server. The CONFIGURE DEFAULT DEVICE TYPE CLEAR command clears the configured default device and returns it to DISK (the default setting). The CONFIGURE setting s for duplexing only affect backups of datafiles, control files and archived logs into backup sets, and do not affect image copies. The All legitimate Oracle experts Please For example, you can enter one of the following commands: You can disable the exclusion feature for cwmlite and example as follows: RMAN includes these tablespaces in future whole database backups. These channels play a huge part in the working of RMAN, to make After connecting to the target database and recovery catalog (if you use one), run the SHOW ARCHIVELOG BACKUP COPIES or SHOW DATAFILE BACKUP COPIES commands. there is a chance of losing it and thus, losing the option to This scenario assumes that the following service name in the tnsnames.ora connects to the target database using the shared server architecture, where inst1 is a value of the SERVICE_NAMES initialization parameter: Create a net service name in the tnsnames.ora file that connects to the non-shared SID. Normally, it This example shows a snapshot location that is determined by the default rule: This example shows a snapshot control file that has a nondefault filename: Use the CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'filename' command to change the name of the snapshot control file. You can also set the snapshot control file name to a raw device: If one RMAN job is already backing up the control file while another needs to create a new snapshot control file, you may see the following message: Under normal circumstances, a job that must wait for the control file enqueue waits for a brief interval and then successfully retrieves the enqueue. Wanted! The default value is given in bytes and is rounded down to the lowest kilobyte value. servicesApplication The following examples show possible configurations: If you use the duplexing feature in conjunction with multiple FORMAT strings, then you can name each individual backup set copy. At that time, manual channel allocation can come in handy. A tablespace does not change often and therefore should be backed up on a different schedule from other backups. Nevertheless, you can connect specified sessions to dedicated servers, even when the target is configured for a shared server. The SHOW CHANNEL, SHOW DEVICE TYPE and SHOW DEFAULT DEVICE TYPE commands are used to display the current configured channel settings. Then, obtain and install the third-party media management module for integration with the database server. To show the snapshot control file filename: After connecting to the target database and recovery catalog (if you use one), run the SHOW SNAPSHOT CONTROLFILE command. The value set by the CONFIGURE MAXSETSIZE command is a default for the given channel. ApplicationsOracle Excel-DB, Expert Oracle Database Tips by Donald BurlesonMarch 25, 2015. For example, to connect to a dedicated session you can issue: To connect to a shared server session, you can issue: Connect to the target database (and optionally the recovery catalog) with the dedicated service name. Ion For example, enter: Sample output for SHOW SNAPSHOT CONTROLFILE follows: RMAN cannot connect to the target database through a shared server dispatcher. Note that you cannot disable the default device type: it is always either DISK (default setting) or sbt. Details of the effect of various combinations of these parameters on online redo log creation can be found inOracle Database SQL Reference in the description of the LOGFILE clause of the CREATE DATABASE statement. is better to let the allocation be automatic only, but at times,
Some media managers have limits on the maximum size of files that they can back up or restore. command. The following shows sample output: Your operating system specific database documentation and the documentation supplied by your media vendor for instructions on how to achieve media manager integration on your platform, "After Installation of Media Manager, RMAN Channel Allocation Fails: Scenario" for troubleshooting scenarios involving media manager problems. For example, assume that you run the following: In this case, RMAN clears the settings for CHANNEL 3, but leaves the settings for the generic DISK channel (the channel with no number manually assigned) intact.