1、RMAN与带库Skip HeadersOracle9i Recovery Manager Users GuideRelease 2 (9.2)Part Number A96566-01HomeBook ListContentsIndexMaster IndexFeedback8Configuring the Recovery Manager EnvironmentThis chapter describes how to perform setup and configuration tasks. This chapter contains these topics: Configuring
2、RMAN to Make Backups to a Media Manager Configuring Automatic Channels Configuring the Control File and Server Parameter File Autobackup Configuring the Backup Retention Policy Configuring the Maximum Size of Backup Sets Configuring Backup Optimization Configuring the Number of Backup Copies Configu
3、ring Tablespaces for Exclusion from Whole Database Backups Setting Globalization Support Environment Variables for RMAN Configuring the Snapshot Control File Location Setting Up RMAN for Use with a Shared Server Setting Up a Recovery Catalog Configuring RMAN to Make Backups to a Media ManagerOn most
4、 platforms, to back up to and restore from sequential media such as tape, you must integrate a media manager with Oracle. A media manager is not an Oracle product and must be obtained from a third-party vendor. If you choose to use RMAN with a media manager, then you must obtain all product-specific
5、 information from the vendor.This section describes the generic steps for configuring RMAN for use with a media manager. The actual steps depend on the media management product that you install and the platform on which you are running Oracle.Read the following sections in order when configuring the
6、 media manager:1. Prerequisites for Using a Media Manager with RMAN 2. How Oracle Interacts with the Media Manager 3. Integrating RMAN with the Media Manager: Basic Steps 4. Testing Whether the Media Manager Library Is Integrated Correctly 5. Configuring Automatic Channels for Use with a Media Manag
7、er See Also: Media Management for an overview of media management software and its implications for RMANPrerequisites for Using a Media Manager with RMANBefore you can begin using RMAN with a media manager, you must install it and make sure that RMAN can communicate with it. Instructions for this pr
8、ocedure should be available in the media manager vendors software documentation.Depending on the product that you are installing, the following basic steps apply:1. Install and configure the media management software on the target host or production network. No RMAN integration is required at this s
9、tage. 2. Ensure that you can make non-RMAN backups of operating system files on the target database host. This step makes later troubleshooting much easier. Refer to your media management documentation to learn how to back up files to the media manager. 3. Obtain and install the third-party media ma
10、nagement module for integration with the Oracle server. This module must contain the library that Oracle loads when accessing the media manager. If you have not performed the preceding steps, then do not proceed with the media management configuration.How Oracle Interacts with the Media ManagerTo ma
11、ke backups to a media manager, RMAN must communicate with a media management library. The procedure for using RMAN with a media manager in Oracle9i has not changed from previous releases.The loading of a media manager library is operating system specific. When you RMAN allocates channels, it uses th
12、e following algorithm when deciding which library to load:1. Attempts to load the library indicated by the SBT_LIBRARY parameter in the ALLOCATE CHANNEL or CONFIGURE CHANNEL command. If the SBT_LIBRARY parameter is not specified, then Oracle proceeds to the next step. 2. Attempts to load the default
13、 media management library. The filename of the default library is operating system specific. On UNIX, the library filename is $ORACLE_HOME/lib/libobk.so, with the extension name varying according to platform: .so, .sl, .a, and so forth. On Windows NT the library is named %ORACLE_HOME%binorasbt.dll.
14、Note: The default media management library file is not part of the standard Oracle installation as in previous releases, so you can only create it by installing third-party media management software.3. If Oracle is unable to locate the default library in the previous step, then RMAN issues an ORA-27
15、211 error and exits. Whenever channel allocation fails, Oracle writes a trace file to the USER_DUMP_DEST directory. The following shows sample output:SKGFQ OSD: Error in function sbtinit on line 2278SKGFQ OSD: Look for SBT Trace messages in file /oracle/rdbms/log/sbtio.logSBT Initialize failed for /
16、oracle/lib/libobk.soIntegrating RMAN with the Media Manager: Basic StepsAfter you install the media management software, the media management library should already be integrated with the Oracle server. You should not have to perform further integration. However, you may choose to follow the procedure in t
copyright@ 2008-2022 冰豆网网站版权所有
经营许可证编号:鄂ICP备2022015515号-1