CA ARCserve Backup para Linux Agente para Oracle

CA ARCserve Backup for Linux
Agent for Oracle Guide

r16
This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation) is for your informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA. Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy. The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors. Copyright 2011 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
CA Technologies Product References

This document references the following CA Technologies products:

BrightStor Enterprise Backup CA Antivirus CA ARCserve Assured Recovery CA ARCserve Backup Agent for Advantage Ingres CA ARCserve Backup Agent for Novell Open Enterprise Server for Linux CA ARCserve Backup Agent for Open Files on Windows CA ARCserve Backup Client Agent for FreeBSD CA ARCserve Backup Client Agent for Linux CA ARCserve Backup Client Agent for Mainframe Linux CA ARCserve Backup Client Agent for UNIX CA ARCserve Backup Client Agent for Windows CA ARCserve Backup Enterprise Option for AS/400 CA ARCserve Backup Enterprise Option for Open VMS CA ARCserve Backup for Linux Enterprise Option for SAP R/3 for Oracle CA ARCserve Backup for Microsoft Windows Essential Business Server CA ARCserve Backup for UNIX Enterprise Option for SAP R/3 for Oracle CA ARCserve Backup for Windows CA ARCserve Backup for Windows Agent for IBM Informix CA ARCserve Backup for Windows Agent for Lotus Domino CA ARCserve Backup for Windows Agent for Microsoft Exchange Server CA ARCserve Backup for Windows Agent for Microsoft SharePoint Server CA ARCserve Backup for Windows Agent for Microsoft SQL Server CA ARCserve Backup for Windows Agent for Oracle CA ARCserve Backup for Windows Agent for Sybase CA ARCserve Backup for Windows Agent for Virtual Machines CA ARCserve Backup for Windows Disaster Recovery Option CA ARCserve Backup for Windows Enterprise Module
CA ARCserve Backup for Windows Enterprise Option for IBM 3494 CA ARCserve Backup for Windows Enterprise Option for SAP R/3 for Oracle CA ARCserve Backup for Windows Enterprise Option for StorageTek ACSLS CA ARCserve Backup for Windows Image Option CA ARCserve Backup for Windows Microsoft Volume Shadow Copy Service CA ARCserve Backup for Windows NDMP NAS Option CA ARCserve Backup for Windows Storage Area Network (SAN) Option CA ARCserve Backup for Windows Tape Library Option CA ARCserve Backup Patch Manager CA ARCserve Backup UNIX and Linux Data Mover CA ARCserve Central Host-Based VM Backup CA ARCserve Central Protection Manager CA ARCserve Central Reporting CA ARCserve Central Virtual Standby CA ARCserve D2D CA ARCserve D2D On Demand CA ARCserve High Availability CA ARCserve Replication CA VM:Tape for z/VM CA 1 Tape Management Common Services eTrust Firewall Unicenter Network and Systems Management Unicenter Software Delivery Unicenter VM:Operator
Contact CA
Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product
Providing Feedback About Product Documentation If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected]. To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.
Documentation Changes
The following documentation updates have been made since the last release of this documentation:

Rebranded to CA Technologies. Updated to include user feedback, enhancements, corrections, and other minor changes to help improve the usability and understanding of the product or the documentation itself.
Contents
Chapter 1: Introducing the Agent for Oracle 11
Agent Features ........................................................................................................................................................... 11 Agent Functionality .................................................................................................................................................... 12 Database Backups ............................................................................................................................................... 12
Chapter 2: Installing the Agent
13
Installation Prerequisites ........................................................................................................................................... 13 The Agent in a RAC Environment ............................................................................................................................... 13 Install the Agent ......................................................................................................................................................... 14 Perform Post-Installation Tasks ................................................................................................................................. 15 Check ARCHIVELOG Mode .................................................................................................................................. 16 Start ARCHIVELOG Mode .................................................................................................................................... 17 Automatic Archiving ............................................................................................................................................ 17 ARCHIVELOG to NOARCHIVELOG Mode Comparison ......................................................................................... 19 Configure the Agent ............................................................................................................................................ 20 Create an RMAN Catalog..................................................................................................................................... 22 Post-Installation Tasks Required for Recovery Manager ........................................................................................... 24 The SBT 1.1 and SBT 2.0 Interfaces ..................................................................................................................... 24 How the SBT Library Uses the sbt.cfg Parameter File ......................................................................................... 25 How the SBT Inteface Uses libobk Library Files .................................................................................................. 25 Oracle and CA libobk Library Files ....................................................................................................................... 26 Add the Oracle User as a CA ARCserve Backup User Equivalency ...................................................................... 27 Registering the Agent for Oracle ................................................................................................................................ 27 Remove the Agent ...................................................................................................................................................... 28
Chapter 3: Backing Up Data
29
Backup Basics ............................................................................................................................................................. 29 Backup Strategy .................................................................................................................................................. 29 Oracle Server Organization ................................................................................................................................. 30 Online Redo Log Files .......................................................................................................................................... 31 Multiple Databases ............................................................................................................................................. 31 Backups ...................................................................................................................................................................... 32 Recovery Manager (RMAN) ................................................................................................................................ 32 Types of Backups ................................................................................................................................................. 33 Back Up Oracle Database Offline ........................................................................................................................ 33 Back Up Oracle Database Online......................................................................................................................... 37
Contents 7
Multistreaming Backups ..................................................................................................................................... 41 Back Up with the Number of Channels (Streams) Option ................................................................................... 41 Back Up Using RMAN Scripts in the Agent .......................................................................................................... 42 Back Up Manually with RMAN ............................................................................................................................ 43 RMAN Command Line Scripts ............................................................................................................................. 43 Backup Limitations ..................................................................................................................................................... 44
Chapter 4: Restoring and Recovering Data
45
Restore and Recovery Basics ...................................................................................................................................... 45 Restore ....................................................................................................................................................................... 45 Restore Types ...................................................................................................................................................... 46 Restore Manager ........................................................................................................................................................ 46 Restore Options .................................................................................................................................................. 48 Restore Views...................................................................................................................................................... 50 Restore Databases and Database Objects .......................................................................................................... 50 Restore Archived Logs and Control Files ............................................................................................................. 52 Restore Parameter File ....................................................................................................................................... 53 Restore Point-in-Time ......................................................................................................................................... 53 Recovery Manager (RMAN) and Restoring a Database to Another Host ............................................................ 54 Database Recovery ..................................................................................................................................................... 56 Restore Manager Recovery ................................................................................................................................. 56 Files the Agent Cannot Recover .......................................................................................................................... 57 Oracle Constraints on Recovery Operations ....................................................................................................... 58 Manual Recovery ................................................................................................................................................ 58 Recover from Offline Full Backups ...................................................................................................................... 60 Restore and Recovery Limitations .............................................................................................................................. 60
Appendix A: Locating Directories and Files
61
Agent Directory Locations .......................................................................................................................................... 61 Agent File Locations ................................................................................................................................................... 61 Agent Files Under Data Directory ....................................................................................................................... 62 Agent Files Under Logs Directory ........................................................................................................................ 62
Appendix B: Troubleshooting
63
Assign Alias Name ...................................................................................................................................................... 63 RMAN script back up for multiple channels fails ....................................................................................................... 63 Tips ............................................................................................................................................................................. 64 Messages .................................................................................................................................................................... 64 RMAN Messages ........................................................................................................................................................ 69 Unable to run ARCHIVELOG Mode ...................................................................................................................... 70
8 Agent for Oracle Guide
RMAN Exits With an Error during Backup or Restore ......................................................................................... 70 RMAN Job Exits with Agent Error ........................................................................................................................ 71 Until End of Logs Option Does Not Work ............................................................................................................ 71 Backup or Restore Fails ....................................................................................................................................... 71 Too Many oragentd_<job id> Log Files are Accumulating .................................................................................. 72 Oracle Permission Errors During Restore Operation .......................................................................................... 72 Restore Oracle Data Files in a Different Directory .............................................................................................. 72 Agent Fails with Oracle Password is Missing in the Job Message ....................................................................... 73 Error Messages While Trying to Run Concurrent Backups on the Same Database ............................................ 73
Appendix C: Configuring the agent.cfg and sbt.cfg Files
75
The agent.cfg Configuration File ................................................................................................................................ 75 Enable Debug Option .......................................................................................................................................... 76 Restore Old Backup to an Alternate Location ..................................................................................................... 77 The sbt.cfg Parameter File ......................................................................................................................................... 77 Set the NLS_LANG Parameter .................................................................................................................................... 83
Glossary Index
85 87
Contents 9
Chapter 1: Introducing the Agent for Oracle

This section contains the following topics: Agent Features (see page 11) Agent Functionality (see page 12)
Agent Features
The agent offers the following features that help improve backup and restore performance:
Fully Integrated with RMAN--The agent is fully integrated with Recovery Manager (RMAN), an Oracle utility that lets you back up, restore, and recover databases. Using the agent user interface, you can access all RMAN options for the backup, restore, and recovery operations. The agent generates RMAN scripts to perform the desired operation, and lets you save and identify the RMAN scripts that are generated. For more information about Recovery Manager, see the Oracle documentation. Cross Product Interoperability--The agent lets you perform a restore through RMAN even if you performed a backup using the agent. Alternatively, you can perform a restore using the agent if you had performed the backup using RMAN. Multistreaming--The agent uses the RMAN parallel input/output capabilities, namely multistreaming through multiple channels. In addition, the agent derives other capabilities from RMAN such as load-balancing among channels and node affinity and channel failover in RAC environments. Staging--The agent lets you perform a staging backup job of multiple Oracle RMAN database instances in a single job. Media Maximization--The agent uses media maximization to help optimize tape usage in GFS Rotation jobs and ensure that any wasted space on these tapes will be minimized. Cross Platform Backups--The agent can back up Oracle databases on Linux platforms to CA ARCserve Backup servers running on Windows platforms. This capability provides centralized backups.
Chapter 1: Introducing the Agent for Oracle 11
Agent Functionality
Agent Functionality
The agent and Oracle reside on the same computer. When CA ARCserve Backup starts to back up a database object, it sends a request to the agent. The agent retrieves the object from Oracle and sends it to CA ARCserve Backup, where the object is backed up to media. Similarly, the agent transfers the database object when the file is restored from media. For more information about backing up databases and database objects, see the chapter Backing Up Data. For more information about Oracle backup and recovery procedures, see the Oracle documentation. Note: In a Real Application Cluster (RAC) environment, a copy of the agent must reside on at least one node in the environment. In addition, this node must have access to all archive logs. Otherwise, the backup operation is essentially the same.
Database Backups
You can perform an online database backup using the following method:
To perform a database back up, the Agent for Oracle generates an RMAN script based on the options you select in the agent user interface (that is, the Backup Manager). The agent then calls RMAN to execute this script. When RMAN starts, it generates other agent jobs to perform the actual backup. These agent jobs receive data blocks from the RMAN and then sends them to CA ARCserve Backup for backup to the media drive.
Note: The agent and CA ARCserve Backup can back up a complete database or objects within the database. You can also perform an offline backup with the agent using the following procedure:

To perform offline database backups, the agent puts the database in a quiescent state before beginning the backup process. This quiescent state allows the database to remain accessible to RMAN throughout the backup process, but does not let anyone access the database or run transactions.
Chapter 2: Installing the Agent

This section contains the following topics: Installation Prerequisites (see page 13) The Agent in a RAC Environment (see page 13) Install the Agent (see page 14) Perform Post-Installation Tasks (see page 15) Post-Installation Tasks Required for Recovery Manager (see page 24) Registering the Agent for Oracle (see page 27) Remove the Agent (see page 28)
Installation Prerequisites
Before installing the Agent for Oracle, verify that the following applications are installed and working properly:

This release of the CA ARCserve Backup base product Appropriate variety and version of Linux Appropriate version of Oracle Server
Note: For information about the appropriate version of Linux and the appropriate version of Oracle Server for your environment, see the Readme. Before you start installing the agent, you must have administrator privileges with root access to install software on the machines on which you plan to install the agent. Note: Contact your CA ARCserve Backup administrator to obtain the proper privileges if you do not have them.
The Agent in a RAC Environment

To configure the agent in a Real Application Cluster (RAC) environment, you must install and configure the agent on at least one node that is a part of the RAC cluster and that has access to all archive logs. You can install the agent on more than one node in the RAC, but each node must also have access to all the archive logs. If you do install the agent on multiple nodes, note that the backup is executed from the node selected in the Backup Manager.
Chapter 2: Installing the Agent 13
Install the Agent
To enable the Agent for Oracle to access all archive logs for the recovery process similar to the way Oracle accesses them, you need to follow Oracles recommendation for building a RAC environment. Oracle requires access to all required archive logs, whatever their origin, in the RAC environment during recovery. To allow the Agent for Oracle access to all the archived logs, you should do one of the following:

Put all required archive logs on a shared disk Put all required archive logs on a mounted NSF disk Use the replication of the archive logs
Install the Agent

The Agent for Oracle is a client program you install on one of the following:

The server on which Oracle Server resides At least one node in a Real Application Cluster (RAC) environment that has access to all archive logs
The Agent for Oracle follows the standard installation procedure for the CA ARCserve Backup system components, agents, and options. For information about installing CA ARCserve Backup, see the Implementation Guide. This section describes the installation prerequisites and considerations for the agent, and provides detailed instructions for all post installation tasks. Note: You must install the agent on all Oracle database servers managed by CA ARCserve Backup.
Perform Post-Installation Tasks

After you have installed the agent, complete the following post-installation tasks: 1. 2. 3. Check whether Oracle Server is operating in ARCHIVELOG mode. Start ARCHIVELOG mode if it is not running. Enable the database for automatic archiving. Note: For an Oracle 10g and 11g database, after you start archivelog mode, Oracle enables automatic archiving for you. For all other databases, you must follow all the steps in the Automatic Archiving section to enable automatic archiving. 4. 5. Configure the agent by running the orasetup program. Although optional, we strongly recommend that you create an RMAN catalog. We also recommend that you create this catalog in a database other than the one RMAN manages.
Important! You must perform these post-installation tasks on each machine on which you have installed the agent, including when the agent is installed on a RAC node. More information: Enable Automatic Archiving for Oracle Installation Using PFILE (see page 18) Configure the Agent (see page 20) Create an RMAN Catalog (see page 22)
Check ARCHIVELOG Mode

You must enable the ARCHIVELOG mode to archive the redo logs.Use the following procedure to check if the ARCHIVELOG mode is enabled. To check if the ARCHIVELOG mode is enabled 1. 2. Log into Oracle server as an Oracle user with SYSDBA equivalent privileges. Enter the following command at the SQL*Plus prompt:
ARCHIVE LOG LIST;
This command displays Oracle's archive log settings for this instance. For the agent to function properly the following should be set: Database log mode: Archive Mode Automatic archival: Enabled
Start ARCHIVELOG Mode

You must start the ARCHIVELOG MODE to backup the database after installing the agent. To start ARCHIVELOG mode 1. 2. Shut down Oracle Server. Execute the following statements in Oracle: At the SQL*Plus prompt in Oracle:
CONNECT SYS/SYS_PASSWORD AS SYSDBA STARTUP MOUNT EXCLUSIVE ALTER DATABASE ARCHIVELOG; ALTER DATABASE OPEN; ARCHIVE LOG START;
If you are not using a flash recovery area with your Oracle 10g or Oracle 11g server, you must include the following entries in either the PFILE or the SPFILE:
LOG_ARCHIVE_DEST_1="/opt/Oracle/oradata/ORCL/archive" LOG_ARCHIVE_FORMAT="ARC%S_%R.%T"
Note: With Oracle 10g or Oracle 11g, the LOG_ARCHIVE_START and LOG_ARCHIVE_DEST entries are considered obsolete and should not be made, in either the PFILE or the SPFILE. For more information about why to start the Archive Log Mode, see the Oracle documentation.
Automatic Archiving
To back up tablespaces from an online or offline database, you must configure the database for automatic archiving. Note: For an Oracle 10g and 11g database, Oracle enables automatic archiving after you start archivelog mode. For all other databases, you must follow all the appropriate steps in this section to enable automatic archiving. More information: Perform a Backup in Offline Mode (see page 34) Perform a Backup in Online Mode (see page 38)
Enable Automatic Archiving for Oracle Installation Using PFILE

To configure the database for automatic archiving if your Oracle installation is configured to use PFILE, add the following log parameter lines to the INIT(SID).ORA file in your $ORACLE_HOME/dbs directory:
LOG_ARCHIVE_START=TRUE LOG_ARCHIVE_DEST=<archive log directory> LOG_ARCHIVE_FORMAT=%t_%s.dbf
Some of the log parameters include the following:

LOG_ARCHIVE_START--Enables automatic archiving. LOG_ARCHIVE_DEST--Specifies the path to the archived redo log files. The Agent for Oracle queries Oracle Server parameters for the archive log destination in the following order: LOG_ARCHIV_DEST, LOG_ARCHIVE_DEST_1 and so on through LOG_ARCHIVE_DEST_10. The agent backs up the archive logs from the first local destination it finds. LOG_ARCHIVE_FORMAT--Specifies the filename format for the archived redo log files where %S specifies the log sequence number and %T specifies the thread number. For example, ARC%S.%T is acceptable. Important! Use a separator between numerical values. For example, %S.%T. If you omit the separator, archive log file names cannot be parsed because there is no way to determine which part is %S and which part is %T. In addition, this could inadvertently create multiple archive logs with the same name.
Enable Automatic Archiving for Oracle Installation Using SPFILE

You can enable automatic archiving for the Oracle installation using SPFILE. To enable automatic archiving for Oracle installation using SPFILE 1. Verify the value of the log parameters by entering the following command at the SQL*Plus prompt:
show parameter log
2.
If the parameters do not have the correct values, change them by entering the following commands at the SQL*Plus prompt after you shut down the server:
CONNECT SYS/SYS_PASSWORD AS SYSDBA STARTUP MOUNT EXCLUSIVE ALTER SYSTEM SET LOG_ARCHIVE_START = TRUE SCOPE = SPFILE; ALTER SYSTEM SET LOG_ARCHIVE_DEST="/opt/Oracle/oradata/ORCL/archive" SCOPE = SPFILE; ALTER SYSTEM SET LOG_ARCHIVE_FORMAT="ARC%S.%T" SCOPE = SPFILE;
Note: The actual value of LOG_ARCHIVE_DEST is specific to your environment. 3. Restart the Oracle instance to make the changes effective.
For more information about setting automatic archiving, see the Oracle documentation.
ARCHIVELOG to NOARCHIVELOG Mode Comparison

The following table explains the advantages and disadvantages of ARCHIVELOG mode and NOARCHIVELOG mode.
Mode ARCHIVELOG mode
Advantages
Disadvantages
You can perform hot It requires additional disk space to backups (backups when the store archived log files. However, the database is online). agent offers the option to purge the logs after they have been backed up, giving you the opportunity to free The archive logs and the disk space if you need it. last full backup (offline or online) or an older backup can completely recover the database without losing any data because all changes made in the database are stored in the log file.
Mode NOARCHIVELOG mode
Advantages
Disadvantages
It requires no additional If you must recover a database, you disk space to store archived can only restore the last full offline log files. backup. As a result, any changes made to the database after the last full offline backup are lost. Database downtime is significant because you cannot back up the database online. This limitation becomes a very serious consideration for large databases.
Important! Because NOARCHIVELOG mode does not guarantee Oracle database recovery if there is a disaster, the Agent for Oracle does not support this mode. If you need to maintain Oracle Server in NOARCHIVELOG mode, then you must backup full Oracle database files without the agent using CA ARCserve Backup while the database is offline to ensure disaster recovery. When you are working with RMAN, ensure that the database runs in ARCHIVELOG mode.
Configure the Agent

After installing the agent, you must run the orasetup program to configure the agent properly as mentioned in the instructions. To run the orasetup program 1. 2. Change to the agent home directory. Enter the following command to start the orasetup program:
./orasetup
3.
The orasetup program prompts you to enter the agent home directory. The default setting is the current directory.

If you want to select the default, press Enter. If the agent home directory differs from the current directory, enter the path name for that directory, and then press Enter.
4.
The orasetup program asks you if you are planning to back up data on the local Data Mover.

If Data Mover is installed locally and you are planning to back up data on the local Data Mover, enter y and press Enter. If Data Mover is not installed locally or you are not planning to back up data on the local Data Mover, enter n and press Enter.
5. 6.
The orasetup program asks you if Oracle is installed on this machine. Enter y, and then press Enter. The orasetup program asks you if a Recovery Manager catalog will be used to handle the database backups. If you intend to do this, enter y, and then press Enter. Note: We recommend using an RMAN catalog when performing a backup because RMAN stores all relative backup information in this catalog, providing your data with the best protection possible.
7.
If this is a new configuration, the orasetup program asks you to register all of the Oracle System IDs (SIDs) to be used with CA ARCserve Backup. If this is not a new installation, the orasetup program asks you if the existing configuration files should be recreated. If you want to keep your existing instance.cfg and sbt.cfg files, enter n. Note: The orasetup program creates two configuration files: instance.cfg and sbt.cfg.
If these files already exist when you run orasetup and you do not want to overwrite them, enter n. The instance.cfg file and sbt.cfg file remain unchanged and orasetup creates sbt.cfg.tmpl, a template file. You can then use this template file to adjust the sbt.cfg file manually. If you select to overwrite the configuration files, orasetup creates new instance.cfg and sbt.cfg files that overwrite your existing instance.cfg and sbt.cfg files. The agent uses the instance.cfg file to register new instances of Oracle or to make modifications. You can configure the instance.cfg file at any time.
8. 9.
The orasetup program prompts you to print the content of the oratab file. You then choose the ones you want to configure. The orasetup program prompts you to provide the Oracle instance ID to be used by the agent (for example, Database1, Database2). When finished, click Enter.
10. Enter the ORACLE_HOME environment value for the Oracle instance you entered in the previous step. When finished, press Enter. 11. If you answered yes to the question about whether you will be using an RMAN catalog to handle the database backups, enter the name of the Oracle Net service that will access the database containing the RMAN catalog for this instance.
12. The orasetup program asks you to enter the number of days the Oracle agent log files should be kept before being automatically deleted. The default value is 30 days. In response, do one of the following:

If the default is acceptable, press Enter. If you want to set the number of days to a number other than 30, enter that number, and then press Enter. If you do not want to have the log files deleted automatically, enter 0.
13. The orasetup program asks you enter the number of days the RMAN scripts generated by the agent should be kept before being automatically deleted. The default value is 30 days. In response, do one of the following:

If the default is acceptable, press Enter. If you want to set the number of days to a number other than 30, enter that number, and then click Enter. If you do not want to have the RMAN scripts deleted automatically, enter 0.
14. The orasetup program asks you to enter the name of a user who can connect to this host. 15. The orasetup program asks you to enter the password for that user.
Create an RMAN Catalog

Recovery Manager (RMAN) is an Oracle utility that you can use to back up, restore, and recover database files. RMAN performs important backup and recovery procedures, and greatly simplifies the task that administrators perform during these procedures. Using RMAN and CA ARCserve Backup, you specify your own RMAN scripts to perform backups. You can also use RMAN directly to back up any online database object by connecting directly to RMAN with or without a recovery catalog at the command line. Note: When using the agent or RMAN to back up, we recommend that you use a recovery catalog installed in a separate database. After backing up an Oracle database using RMAN, you can restore the database using either the agent or RMAN. Similarly, if you back up an Oracle database using the Agent for Oracle, you can restore the database using either RMAN or the agent.
For more information about the Recovery Manager, see the Oracle documentation. You can use the RMAN catalog when performing a backup as RMAN stores all relative backup information in this catalog. Without the catalog, RMAN will rely only on control files to manage backups. This is very risky because if all the control files are lost, RMAN will not be able to restore the database. In addition, you will not be able to restore your control files and your database will be lost. Note: Ensure that the Catalog Database is available while performing backup and restore jobs using RMAN catalog. To create an RMAN catalog Note: Because RMAN relies heavily on this catalog when restoring, you should create it in a separate database (that is, a database other than the one being backed up). 1. Create a new tablespace using this SQL*Plus command:
* create tablespace <RMAN catalog tablespace> datafile <datafile name> size <datafile size> m;
2.
Create the user who will be the owner of the RMAN catalog by entering this command:
* create user <RMAN catalog owner> identified by <password> default tablespace <RMAN catalog tablespace> quota unlimited on <RMAN catalog tablespace>;
3.
Assign the correct privileges to this user by using the following command:
* grant recovery_catalog_owner to <RMAN catalog owner>;
4.
Open a new command prompt and run the following command to connect to the catalog database of RMAN:
rman catalog <RMAN catalog owner>/<RMAN catalog password>@rmandb
where rmandb is the TNS Name for the RMAN catalog database. 5. Create a catalog using this command:
create catalog;
Post-Installation Tasks Required for Recovery Manager
6.
Connect to the catalog database and target database of RMAN.

*rman target <user(sys) who has sysdba privilege>/< password for user(sys)>@targetdb catalog <RMAN catalog owner>/<RMAN catalog password>@rmandb
where rmandb is the TNS Name for the RMAN catalog Database and the targetdb is the TNS Name for the Target Database. 7. Execute the following command.
register database;
For more information about using the Recovery Manager, see the Oracle Documentation. Important! If you are not using an RMAN catalog, you need to manage your control files on your own either by using a file system backup or by mirroring the control files for fault tolerance.

To use Oracle Recovery Manager (RMAN), you must perform the following post-installation tasks:
Use library files by performing one of these actions:

Relink Oracle to use the CA Technologies libobk library files. Create the $ORACLE_HOME/lib/libobk.s* symbolic link to point to the CA Technologies libobk library. Use the SBT_LIBRARY parameter in the RMAN script.
Add the client host definition in the CA ARCserve Backup database if not done already. Add the Oracle user who owns the Oracle database files as a CA ARCserve Backup user equivalency. Set the RMAN environment variables.
The SBT 1.1 and SBT 2.0 Interfaces

The SBT (Systems Backup to Tape) 1.1 and SBT 2.0 interfaces are the Oracle APIs (Application Programming Interfaces) that enable CA ARCserve Backup to provide backup and restore capabilities to RMAN. These interfaces use the sbt.cfg parameter file and the CA ARCserve Backup ca_backup and ca_restore commands to initiate backup and restore operations from RMAN.
How the SBT Library Uses the sbt.cfg Parameter File

The SBT library uses the sbt.cfg parameter file to interact with the agent. This file contains various user-defined parameters that are passed to CA ARCserve Backup when you submit backup and restore jobs through the ca_backup and ca_restore commands. The orasetup program creates the initial sbt.cfg configuration file during agent setup. In addition, orasetup automatically encrypts the password and puts it in the sbt.cfg file (SBT_PASSWORD). If you want to modify the password, you must first execute cas_encr <password> to receive the ASCII encrypted value. An example result of the cas_encr command looks similar to this:
# cas_encr password CAcrypt:HGJD92748HNNCJSFDHD764
After you receive this value, you must copy the entire value including the CAcrypt string as the value for the SBT_PASSWORD variable in the sbt.cfg file. Important! Before using cas_encr, you must modify the library path to include the common agent directory. For example, #LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/CA/ABcmagt To set the library path for your Linux operating system follow this guideline:
LD_LIBRARY_PATH=opt/CA/ABcmagt:$LD_LIBRARY_PATH
Note: The sbt.cfg file provides default values if you choose to use RMAN directly.
How the SBT Inteface Uses libobk Library Files

The SBT interface is implemented through libobk library files. Oracle Server provides a default libobk.* library file. However, for your RMAN backup and restore jobs to be successful, RMAN must use one of the following CA Technologies versions of libobk.* instead of the default Oracle version:

libobk.*.1.32 (32-bit implementation of the SBT 1.1 interface) libobk.*.2.32 (32-bit implementation of the SBT 2.0 interface) libobk.*.1.64 (64-bit implementation of the SBT 1.1 interface) libobk.*.2.64 (64-bit implementation of the SBT 2.0 interface)
Some other considerations include:

Oracle 8.0 supports only SBT 1.1. It does not support SBT 2.0. Oracle 8i, 9i, and 10g support both SBT 1.1 and SBT 2.0. We recommend using SBT 2.0 with Oracle 8i, 9i, and 10g. When the agent is installed, the libobk32.* and libobk64.* symbolic links are created in the agent home directory. These symbolic links are used in the RMAN scripts generated by the agent as a value to the SBT_LIBRARY parameter. You can also use these links when you create your own scripts.
Oracle and CA libobk Library Files

For RMAN to use one of the CA Technologies versions of libobk, you may need to relink Oracle. The following section contains the procedure for re-linking Oracle. To re-link Oracle, go to the section for your operating system and perform the procedure that is appropriate for your Linux operating system and your version of Oracle Server. Important! By default, the symbolic link $ORACLE_HOME/lib/libobk.s* exists and points to an existing Oracle library. Before you relink, you must redirect this link to $CAORA_HOME/libobk.s*. For information about redirecting a link that is appropriate for your environment, see your Oracle documentation.
Relink on Linux
To relink Oracle running on Linux, follow these steps: 1. 2. Log on as oracle. Perform one of the following actions:
If you are using Oracle 9i or 10g, switch to the $ORACLE_HOME/lib directory, and enter the following command:
ln -s /opt/CA/ABoraagt/libobk32.so $ORACLE_HOME/lib/libobk.so
If you are using Oracle 8.0.6 or 8i, switch to the $ORACLE_HOME/rdbms/lib directory, and enter the following command:
make -f ins_rdbms.mk ioracle LLIBOBK=$CAORA_HOME/libobk library
Registering the Agent for Oracle
Considerations
To ensure that the Oracle executable is linked properly with the CA Technologies library, switch to the $ORACLE_HOME/bin directory and enter the ldd r command to list the libraries with which the executable is linked. In all the actions in Step 2, libobk library is the fully qualified path where the following libraries are located:

libobk.so.1.32 (32 bit x86 SBT 1 version) libobk.so.2.32 (32 bit x86 SBT 2 version) libobk.so.2.64_IA64 (64 bit Itanium SBT 2 version; no SBT 1 ) libobk.so.2.64_AMD64 (64 bit AMD64 SBT 2 version ; no SBT 1)
The default location is the agent home directory.
Add the Oracle User as a CA ARCserve Backup User Equivalency

To back up, you must add the Oracle user who owns the Oracle database files as a CA ARCserve Backup user equivalency. To add the user, follow these steps: 1. 2. Ensure CA ARCserve Backup is loaded and running. Go to the CA ARCserve Backup home folder and enter the following command:
ca_auth [-cahost CAAB_hostname] equiv add <Oracle_username> <Linux_hostname> CAAB_username [CAAB_username] [CAAB_userpassword]
CAAB_username must be a CA ARCserve Backup administrator. Note: If you have installed the agent in a Real Application Cluster (RAC) environment, you must also add the Oracle user who owns the Oracle database files as a CA ARCserve Backup user equivalency on each node that is a part of the RAC cluster.
Registering the Agent for Oracle

When registering the machine where the Agent for Oracle is installed within CA ARCserve Backup, enter only the actual hostname for the machine. The hostname can be accessed by running the hostname command from the command line on the machine where the Agent for Oracle is installed. When registering an Agent for Oracle, the Oracle user on the Linux server must be given the equivalence of caroot on the Windows server where the base product is installed, with the following command :
ca_auth [-cahost BABhost] -equiv add <Oracle user> <OracleHostName> caroot [caroot_username] [caroot_password]
Remove the Agent
After running this command on the server side, the following error still appears in the activity log during a backup job: CA ARCserve Backup server on xxx.xxx.xxx.xxx failed to authenticate user Oracle. Create a caroot equivalency using ca_auth In this scenario, run the following command on the server where the Agent for Oracle is installed:
[root@rhelu4 BABoraagt]# ./ca_auth -cahost babserver -equiv add Oracle rhelu4 caroot caroot caroot_password [root@rhelu4 BABoraagt]# ./ca_auth -cahost babserver -equiv getequiv Oracle rhelu4 Equivalent ARCserve user for Oracle@rhelu4: caroot
Remove the Agent

To remove the Agent for Oracle from your server, follow the steps on the Installation CD. Important! You must stop Oracle and unlink the libobk libraries before attempting to remove the agent. These steps are appropriate whether you linked Oracle with the CA Technologies libraries or whether you created a softlink in the Oracle lib subdirectory as specified in the post installation tasks.
Chapter 3: Backing Up Data

This section contains the following topics: Backup Basics (see page 29) Backups (see page 32) Backup Limitations (see page 44)
Backup Basics
To back up is to create a copy of a database or database objects on another device (typically a tape drive). Backups are performed using CA ARCserve Backup, the Agent for Oracle, and the Oracle RMAN backup features. Using CA ARCserve Backup, the agent, and Oracle RMAN, you can back up a complete Oracle Server database or individual objects within the database. To back up a complete database, you configure the backup to include all of the objects contained in the database. Typically, you must back up a complete database when you first create the database or when you change the database structure. Tablespaces and other database objects require more frequent backups.
Backup Strategy
You should plan your backup strategy for a database before you create the database. If you do not plan these strategies before you create a database, database recovery may not be possible in certain cases. You should check your backup strategy in a test environment before and after you move to a production system. Testing can minimize problems before they occur in a real situation.
Chapter 3: Backing Up Data 29
Backup Basics
Develop a Backup Strategy

To have a backup strategy, you should:

Perform a full online backup of your Oracle databases. Perform a cold database backup on a regular basis by shutting down the database and performing a file system backup of the Oracle environment. Back up database objects to update the full database backup. Heavily used tablespaces should be backed up frequently to reduce database recovery time. Back up the database control files each time you make a structural change to the database. Mirror Oracle online redo logs. The agent does not perform this procedure. For more information about mirroring online redo logs, see the Oracle Documentation.
For more information about Oracle backup and recovery procedures, see the Oracle documentation.
Oracle Server Organization

Oracle Server is organized into databases that are subdivided into database objects. An Oracle database contains the following types of objects:

Tablespaces that contain data. Tablespaces can consist of multiple data files. Data files that contain the database data. Data files are the physical files that define a tablespace. Online redo log files that contain records of transactions applied to the tablespaces. Control files that describe the structure of the database, including the tablespaces. There can be more than one control file copy for the database. Parameter files that contain the various initialization parameters the database uses when it starts up. Recovery area (for latest Oracle versions) that organizes all recovery-related files and activities for an Oracle database.
Backup Basics
Online Redo Log Files

Oracle Server uses online redo log files to record all entries to the Oracle tablespaces. However, the Agent for Oracle requires archived online redo log files to function properly. For Oracle to create archived redo log files, you must set Oracle to operate in ARCHIVELOG mode. Also, for the agent to back up and restore properly, you must set Oracle to automatically archive online redo log files. Note: For information about setting Oracle so that it operates in ARHIVELOG mode and automatically archives online redo log files, see Perform Post-Installation Tasks (see page 15).
Multiple Databases
If your Oracle configuration has more than one database you can:

View and log in to the databases View and log in to the databases you specified if you reconfigured the agent by running orasetup from the agent home directory. Configure the agent so that the Backup Manager window displays the objects from any specified database. Quickly find the database objects that you want to back up.
Configure a Backup Session for Multiple Database Environment

To set up your backup session to view and log in to the databases you specified during installation on an Oracle configuration containing multiple databases. To configure a backup session for multiple database environment 1. Start CA ARCserve Backup and open the Backup Manager. The Backup Manager opens. 2. 3. On the Source tab, expand the Linux Agent. Under the Linux Agent, click the green square to the left of the host on which Oracle is installed. The Login dialog opens. 4. 5. 6. Enter the system user name and password, and then click OK. Expand the host. Click the green square to the left of the Oracle database. The Database Login dialog opens.
Backups
7. 8.
Enter the Oracle dba user name and password. Click OK. You can now expand the database and select the database objects you want to back up.
Backups
Using the agent, you can back up complete Oracle databases and individual Oracle database objects, such as tablespaces, data files, archived redo log files, control files, parameter files, and the recovery area. You should back up all of the objects in a database immediately after you create the database and maintain a regular backup schedule to ensure smooth recovery in case of database or media failure. CA ARCserve Backup allows you to set and maintain a schedule of automatic backups. Agent backups are performed through scripts the agent sends to the Oracle Recovery Manager (RMAN). These scripts are generated automatically based on the options you choose on the Backup Manager, and are saved under <oracle agent home dir>/rman_scripts. They are saved for the amount of time you specify in the environment variable <DAYS_RMAN_SCRIPTS_RETAINED> in the agent.cfg file.
Recovery Manager (RMAN)

Recovery Manager (RMAN) is an Oracle utility used to back up, restore, and recover database files. RMAN performs important backup and recovery procedures and greatly simplifies the tasks that administrators perform during these procedures. For more information about the Recovery Manager, see the Oracle Backup and Recovery Guide. Using RMAN and CA ARCserve Backup, you specify your own RMAN scripts to perform backups. You can also use RMAN directly to back up any online database object by connecting directly to RMAN with or without a recovery catalog at the command line. Note: When using the agent or RMAN to back up, we recommend you use a recovery catalog installed in a separate database. After backing up an Oracle database using RMAN, you can restore the database using either the agent or RMAN. Similarly, if you back up an Oracle database using the Agent for Oracle, you can restore the database using either RMAN or the agent.
Backups
RMAN Prerequisites
Before you can back up with RMAN and the agent, you must:
Use the Computer Associates libobk library files by performing one of these actions:

Relink Oracle Create the $ORACLE_HOME/lib/libobk.* symbolic link Use SBT_LIBRARY in the RMAN script (depending on the platform and Oracle version)
Add the Oracle user who owns the Oracle database files as a CA ARCserve Backup user equivalency.
Note: For information about performing these tasks, see Post-Installation Tasks Required for Recovery Manager (see page 24).
Types of Backups
Using CA ARCserve Backup and the agent, you can perform several types of backups:

Offline backups Online backups Staging backups Multistreaming (or multi-channels) backups Launch backups by loading your own RMAN scripts in the Backup Manager
Note: You can also use RMAN directly to launch backups at the command line level.
Back Up Oracle Database Offline

Performing an offline backup through the agent puts the database in a quiescent state before the backup process begins. The reason for this is that RMAN must be able to connect to the database; therefore, the database processes must be running and accepting connection. Performing a true offline backup does not allow this connection to occur. The only way to allow RMAN to connect to the database and not have it online is to use the quiescent state, which prevents all user transactions from occurring. Note: To perform a true offline backup, use the agent to back up your database after manually shutting it down. To restore your database, use the agent again, and then manually start up your database.
Backups
Perform a Backup in Offline Mode

You can perform a backup in offline mode using the following procedure. To perform a backup of an Oracle database in offline mode Note: Before opening the Backup Manager, ensure that Oracle Server is running, and be sure to start CA ARCserve Backup and the agent. 1. 2. Open the Backup Manager, select the Source tab, and expand the Linux Agent. Under Linux Agent, click the green square to the left of the host on which Oracle is installed. The Login dialog opens. 3. Enter the host user name and password, and then click OK. The host expands. 4. Click the green square next to the Oracle database you want to back up. The Login dialog opens. 5. Enter the Oracle database dba user name and password, and then click OK. The green square becomes entirely green. Note: Be sure that the Oracle user name and password you use to connect to Oracle has the permission to connect to Oracle using the as sysdba clause. You must be able to connect with and without this clause.
Backups
6.
To set backup options, select the Source tab and then click the Oracle Options tab. The Oracle backup Options dialog opens.
Complete the following fields:

Enter the Oracle DB User Information. Ensure the Use RMAN catalog (Recommended) check box is selected. Note: We recommend that you use the RMAN catalog, otherwise RMAN will rely only on the control files to manage backups. Using only the control files presents a risk in that if the database and all control files are somehow lost, it will prevent RMAN from being able to restore the database. By using the RMAN catalog option, you prevent the possibility of losing the control files backup-related information as well as other valuable information. Also note that if you do not use the RMAN catalog, you limit the possibility of performing a point-in-time recovery. If you choose not to select this option, a warning message displays reminding you of the importance of using the RMAN catalog.
Select the Backup Type as offline mode.
Backups
Choose one the following Backup Methods: Full BackupThis method typically minimizes the number of tapes you will need when restoring the database, but takes more time during the backup. Incremental BackupThis method reduces the backup time, but restoring typically requires more time and tapes to be loaded (that is, the last full backup plus all the incremental ones).
You can select the Number of Channels (Streams).
7.
(Optional) Select the Advanced Oracle Options tab and complete any of these fields if you want to modify the performance of your backup:

Backup Piece Size--Enter a number (in KB) in the Backup Piece Size field if you want RMAN to generate more than a single backup piece. Read Rate (# Buffers)--Enter the maximum number of buffers per second in the Read Rate (# Buffers) field that you want RMAN to use when reading data from the disk. Number of Files per Backup Set--Enter a number in the Number of Files per Backup Set field to limit the number of backup pieces that RMAN should use per backup set. Maximum Number of Opened Files--Enter a number in the Maximum Number of Opened Files field to limit the total number of files that RMAN will open at the same time. Leaving this field empty allows RMAN to use the default value. Backup Set Size (KB)--Enter a number in the Backup Set Size (KB) field to limit the amount of data that should go into a backup set. We recommend that you leave this field empty. Block Size (Bytes)--Enter a value in the Block Size (Bytes) field to allow RMAN to determine the size of the data blocks to send to the agent when performing a backup. Note: If you enter a value in this field, you must also enter the same value when restoring your backup to avoid receiving an error message during the restore process.
Number of Copies--Enter a number between one and four in the Number of Copies field to indicate how many copies of the backup pieces RMAN should generate. Note: To be able to generate more than one copy, you must enable the BACKUP_TAPE_IO_SLAVES option in either your init<sid>.ora or SPFILE file; otherwise you will receive an error message.
Fail the job if number of copies is more than 1 and so many drives are not available--When selected, the backup job fails whenever the number of copies is greater than one and the job cannot gain access to a number of devices sufficient to support them. When not selected, the backup job continues to run even when the number of devices is insufficient for the number of copies. However, the number of copies is reduced.
Backups
Device availability waiting time (minutes)--Specify how long a backup job should wait if it is unable to access the number of devices required. Use with the Continue backup even if some requested devices are not available option. Continue backup even if some requested devices are not available--When selected, a backup job continues to run as long as at least one device is assigned. When not selected, the job fails if it cannot access enough devices within the time specified in the Device availability waiting time field.
8.
Select the Destination tab, and then select the media device group and media in which you want to store the back up. Important! Do not select a specific media or media device group on the Destination tab if you set the Number of Channels option to a number higher than one.
9.
Click the Method/Schedule tab, and choose one of these Schedule Types:

Custom Rotation GFS Rotation
10. Click Start. The Submit Job dialog opens. 11. Schedule the job to run now or at another time. Click OK. The Job Submission dialog opens. 12. Click OK. The job is submitted. You can monitor the job on the Job Status Manager. Refer to the Backup Limitations section of this chapter for information about restrictions related to monitoring your backups. Note: A backup can take up multiple sessions on the media even if you choose only one object. For example, if you enter a limit on the Backup Set Size field on the Advanced Oracle Options tab, it will create multiple sessions.
Back Up Oracle Database Online

Using the Agent for Oracle, you can back up individual Oracle database objects, such as tablespaces, data files, archived redo log files, parameter files, control files, and the recovery area.
Backups
Perform a Backup in Online Mode

To back up an Oracle database online using the agent Note: Before opening the Backup Manager, ensure that Oracle Server is running and that all of the tablespaces in the databases you want to back up are online. Also, be sure to start CA ARCserve Backup and the agent. 1. 2. Open the Backup Manager, select the Source tab, and expand the Linux Agent. Under the Linux Agent, click the green square to the left of the host on which Oracle is installed. The Login dialog opens. Note: If you click the plus sign next to the host, it will expand automatically after you log in successfully. 3. Enter the host user name and password, and then click OK. Note: Expand the host if it did not expand automatically. 4. Select an Oracle database by clicking the green square to its left. The Database Login dialog opens. 5. Enter the Oracle dba user name and password. Note: Be sure that the Oracle user name and password you use to connect to Oracle has the permission to connect to Oracle using the as sysdba clause. You must be able to connect with and without this clause. 6. When backing up a database, a single job called the master job is created in the queue. When the backup begins, the master job calls RMAN, which launches the child jobs. The sub-jobs appear in the job queue.
Backups
7.
If you want to set options for your backup job, select the Source tab and then click the Oracle Option tab:
Complete the following fields:

Enter the database name, if different from the instance name, in the Database Name field. Ensure that the Use an RMAN Catalog (Recommended) check box is selected. Note: We recommend that you use the RMAN catalog, otherwise RMAN will rely only on the control files to manage backups. Using only control files presents a risk in that if the database and all control files are somehow lost, it will prevent RMAN from being able to restore the database. By using the RMAN catalog option, you prevent the possibility of losing the control files backup-related information as well as other valuable information. Also note that by using the RMAN catalog, you will be able to perform a point-in-time recovery if desired. If you choose not to select this option, a warning message displays reminding you of the importance of using the RMAN catalog.
Backups
Enter the catalog owner name and owner password. Select the online mode. Choose one the following Backup Methods:

Full Backup--This method typically minimizes the number of tapes you will need when restoring the database, but takes more time during the backup. Incremental Backup--This method reduces the backup time, but restoring typically requires more time and tapes to be loaded (that is, the last full backup plus all the incremental ones).
Note: Available options pertain to the specific database only. Each database has its own set of options. 8. 9. (Optional) Select the Advanced Oracle Options tab and complete any of these fields if you want to modify the performance of your backup. Click the Destination tab, and select the backup destination. Important! Do not select a specific media or media device group on the Destination tab if you set the Number of Channels option to a number higher than 1. 10. Click the Method/Schedule tab, and choose one of these Schedule Types:

Custom Rotation GFS Rotation
11. Click Submit on the toolbar. The Submit Job dialog opens. 12. Schedule the job to run now or at another time. Click OK. The Job Submission dialog opens. 13. Click OK. The job is submitted. You can monitor the job on the Job Status Manager. Refer to the Backup Limitations section of this chapter for information about restrictions related to monitoring your backups. Note: For more information about customizing backup jobs, see the Administration Guide.
Backups
Multistreaming Backups
If you have more than one drive and volume in your system, you can use the Number of Channels (Streams) option on the Backup Manager to enhance the performance of your backups. After you allocate a certain number of channels to be used for the backup, the agent and RMAN determine how the multiple channels are organized and distributed, and whether all the channels you specified are necessary. In some cases, RMAN may determine that instead of using all the channels you specified, the backup job could be better accomplished by sequentially packaging more than one job (backup piece) per channel, and as a result will use a smaller number of channels for the job. Note: Previous releases of the agent used the Multistreaming option on the Destination tab to accomplish this type of backup. The Number of Channels (Streams) option replaces the Multistreaming option and provides better integration with RMAN, which allows RMAN to handle the multistreaming process rather than the agent. Beginning with this release, the Multistreaming option in the Backup Manager is ignored for Oracle jobs. Important! After specifying more than one channel in the Backup Manager, avoid selecting a specific media or media device group on the Destination tab as this prevents multistreaming from occurring. The number of devices or device groups available on your system dictates the number of jobs RMAN runs simultaneously. For more information about multistreaming, see the Administration Guide.
Back Up with the Number of Channels (Streams) Option

In the following example, you are backing up data to a changer with two tape drives. If you have several single tape drives of the same type and you want to use them all for a multistreaming backup job, ensure that you assign tapes to different device groups. To back up data using multistreaming 1. 2. On the Backup Manager Source tab, select two tablespaces. On the Oracle Options tab, specify a number higher than one in the Number of Channels (Streams) option. Keep in mind that RMAN will determine the actual number of channels needed for the backup job. The value you enter on the Oracle Options tab is the maximum number of channels used by RMAN. (Optional) Specify a name for the Media Pool. You can use either an existing Media Pool name or a new Media Pool you create for the multistreaming job. Note: Do not select a specific media or media device group. Doing so prevents multistreaming from occurring. 4. Click Submit to submit the job. You can monitor the job on the Job Status Manager.
3.
Backups
Back Up Using RMAN Scripts in the Agent

You can create RMAN scripts and launch them from the CA ARCserve Backup GUI. To back up Oracle database using the agent with your RMAN script 1. 2. Open the Backup Manager, select the Source tab, and expand the Linux Agent. Under the Linux Agent, click the green square to the left of the host on which Oracle is installed. The Login dialog opens. Note: If you click the plus sign next to the host, it will expand automatically after you log in successfully. 3. Enter the host user name and password, and then click OK. Note: Expand the host if it did not expand automatically. 4. Select an Oracle database by clicking the green square to its left. The Database Login dialog opens. 5. 6. Enter the Oracle dba user name and password. Click the Advanced Oracle Options tab, and enter the full path of your RMAN script in the Load RMAN Script field. Ensure:

The script must be present on the agent's node and be accessible by the user who is running RMAN (usually the owner of the Oracle instance). Any scripts you provide will override all options you selected in the Backup Manager. If you do not begin the path name with a slash (/), the agent automatically looks in the $CAORA_HOME/rman_scripts directory for the file.
7. 8.
Click the Destination tab, and select the backup destination if desired. Click OK. The Backup Manager submits the job to the queue. You can monitor the job on the Job Status Manager.
For further information about customizing your backup, see the Administration Guide.
Backups
Back Up Manually with RMAN

You can back up a database manually using RMAN. To start RMAN with a recovery catalog and back up a database 1. Open a Command Prompt window and enter the following command to start RMAN:
rman target dbuser/dbuserpassword rcvcat catowner /catownerpassword@rman service name
where: dbuser is the user with dba privileges. dbuserpassword is the dbuser password. catowner is the Oracle user name of the RMAN catalog owner. catownerpassword is the catalog owner password. rman database is the database where the RMAN catalog is installed. 2. Enter the following commands to back up a database:
RMAN> connect target system/manager RMAN> run { 2> allocate channel dev1 type 'sbt_tape'; 3> backup database format '_%u_%p_%c'; 4> release channel dev1; 5> }
Database backup is complete.
RMAN Command Line Scripts

You can write and execute your own RMAN scripts. The following is an example of an RMAN script allocating a single channel to back up a particular data file on a single tape device:
run { allocate channel dev1 type sbt_tape; backup (datafile /oracle/oradata/demo/users01.dbf format _%u_%p_%c); release channel dev1; }
Backup Limitations
Note: To use the Agent for Oracle as a back-end, you must:

Use sbt_tape as the channel type (for Oracle 9i). You can use the _%u_%p_%c format to ensure that the object that is backed up has a unique name.
The following is an example of an RMAN script that uses multistreaming in a backup. It allocates two channels to back up the data to two different tape devices in parallel:
run { allocate channel dev1 type sbt_tape; allocate channel dev2 type sbt_tape; backup filesperset 1 format _%u_%p_%c (datafile /oracle/oradata/demo/users01.dbf, /oracle/oradata/demo/tools01.dbf); release channel dev1; release channel dev2; }
For more information about using RMAN and RMAN scripts, see the Oracle documentation.
Backup Limitations
The following table contains a list of backup limitations:

Do not duplicate the Catalog database SID or share it with any other SID name. This is not supported by Oracle RMAN, and there is no way to pre-determine how much data RMAN will back up. The master job (the one submitted through the Backup Manager) does not show any progress except for the PARAMETER_FILES if they are included in the backup. Opening the monitoring window will not show any progress of the master job, even if sub-jobs are in progress. However, it will show when the master job is complete. Opening the monitoring window of a sub-job will show its progress, but it does not include the progress of other sub-jobs. If the backup job is submitted from Oracle RMAN command line, the job cannot be rescheduled. That is, when you right-click the job option Ready/Hold/Run Now/Modify/Reschedule will be grey in the job queue option.
Chapter 4: Restoring and Recovering Data

This section contains the following topics: Restore and Recovery Basics (see page 45) Restore (see page 45) Restore Manager (see page 46) Database Recovery (see page 56) Restore and Recovery Limitations (see page 60)
Restore and Recovery Basics

To restore is to load a database or one or more database objects from a backup of that database or the objects. A restore overwrites any information in the database with the backed up information. After you restore a database, you must recover it. To recover is to bring a restored database to a consistent point-in-time prior to the point of failure or damage. An Oracle Server database must first be restored and then recovered. After the database has been both restored and recovered successfully, then it is ready for use. You can perform either automatic or manual recoveries.
Restore
To restore is to load a database or one or more database objects from a backup of that database or the objects. A restore overwrites any information in the database with the backed up information. After you restore a database, you must recover it. To recover is to bring a restored database to a consistent point-in-time prior to the point of failure or damage. An Oracle Server database must first be restored and then recovered. After the database has been both restored and recovered successfully, then it is ready for use. You can perform either automatic or manual recoveries. Using CA ARCserve Backup, the agent, and Oracle RMAN, you can restore database objects such as tablespaces, data files, archive log files, and parameter files, either individually or in groups, and restore the control files when you restore a database.
Chapter 4: Restoring and Recovering Data 45
Restore Manager
Restore Types
Using CA ARCserve Backup and the agent, you can perform several types of restore operations:

Restore from backups made through the current release of the agent, using either the Backup Manager or the RMAN command line. Restore from online backups made with a previous release of the agent (through the Backup Manager only). Restore from offline backups made with a previous release of the agent (through the Backup Manager only). Restore from backups made with the RMAN command line with a previous release of the agent (through RMAN only).
Restore Manager
You can perform the various restore jobs using the Restore manager. For more information about the Restore Manager, see the Administration Guide. The Oracle Restore Options tab on the Restore Manager provides the following restore and recovery options:

Oracle DB User Information Use RMAN catalog [Recommended] Number of Channels (Streams) Restore From Latest Backup Restore From Backup Made On Restore From Backup Tag
Note: These restore options are detailed in the Restore Options section of this chapter.
Restore Manager
Recovery Types: Important! When using one of these recovery methods, all logs are reset to the last registered date in the control file, so any data recovered after this date will be lost and cannot be retrieved.

Until SCN (Whole DB Only) Until Log Sequence Number (Whole DB Only) Until Time (Whole DB Only)
Note: Because the logs have been reset, you must perform a full offline backup to ensure that you have a record of the database at that precise moment in time.
No Recovery - Selecting this option restores the data but does not perform any recovery. You must recover the database yourself and then put it back online. You generally use this option when you already know that a restore cannot be recovered, such as when additional restore jobs are required or you need to set up before starting the recovery process. Until the End of Logs - RMAN recovers the database, tablespaces, and data files up to the current time. Until SCN (Whole DB Only) - RMAN recovers the database up to the specified System Change Number (that is, a checkpoint number). This recovery is valid for the entire database only. The database is opened with the resetlogs option. Until Log Sequence Number (Whole DB Only) - RMAN recovers the database up to the specified Archived Log Sequence. This recovery is valid for the entire database only. The database is opened with the resetlogs option. Until Time (Whole DB Only) - RMAN recovers the database up to the specified point in time. This recovery is valid for the entire database only. The database is opened with the resetlogs option. Put Restore Object(s) Online after Recovery - When selected, this option puts the tablespaces and data files online and opens the database after the recovery has been performed.
Restore Manager
In addition, the Advanced Oracle Restore Options tab includes the following options:
Archived Logs Selection:
Do Not Restore - Selecting this option does not restore any of the archived logs. Note: This option is checked automatically.
Time Based - This option restores the archived logs based on the time they were created, and not on the time they were backed up. If you are using this option, you must also enter a value either in the From Time field or in the Until Time field. Thread - This option lets you specify the thread number used to identify the Oracle instance. The default value of the thread is 1 for the Oracle instance in exclusive mode. SCN Based - This option restores the range of archived logs by SCN (System Change Number). Log Sequence Based - This option restores the archived logs by the archived log sequence number.
Include Control File - Select this option if you want to restore the control files. Keep in mind that you should restore the control files only if they are corrupted or lost. Important! Restoring a control file resets all the logs causing you to lose the most recent data once the database is started. There is no way to recover this data.
Block Size (Oracle 9i) - If you use this option, the size of the data blocks must match the block size used during backup; otherwise, the restore will fail. List Backup Sets for Selected Objects - When selected, it sends a request to list all backup sets that include the objects you selected. Note: This option does not restore the selected objects. To restore the selected objects, you must submit another restore job.
Validate Backup Set Number - This option asks RMAN to validate the integrity of a backup without actually restoring it. Load RMAN Script - Use this option to enter the path of your RMAN script. Important! Using this option overrides all options you may have selected in the Restore Manager.
Restore Options
There are several types of restore options available on Source tab of the Restore Manager. Details about each option are listed in the following sections.
Restore Manager
Number of Channels (Streams) Option

When you enter a number in the Number of Channels (Streams) option, the agent tells RMAN the maximum number of channels to use. RMAN then determines how many channels it actually allocates to the restore operation. RMAN submits the jobs in parallel, one for each channel. Note: Because RMAN determines the appropriate number of channels to use, RMAN may use less than the number of channels you specify.
Restore From Latest Backup Option

When you select the Restore From Latest Backup option, the agent tells RMAN to use the latest available backup. Note: No Recovery is the default selection in the Recovery Types section of the Oracle Restore Options tab. Be sure to select one of the other Recovery Types if you want to recover your database after restoring it.
Restore From Backup Made On Option

When you select the Restore From Backup Made On option, you specify the date and time as the upper time limit of the backup from which you want to restore. RMAN will perform the operation on files up to, but not including, the specified time. This option is useful when you have a database that you must bring back to a known state (consistency level). Another time you may want to use this option is when you know the latest backup is inaccessible. In that case, you can use this option in conjunction with the Until End of Logs recovery option to restore the database from an older backup set and "replay" all transactions to bring the database to its latest state. Avoid confusing this option with the Recover Until Time (Whole DB Only) field that was available in earlier versions of the agent. It does not refer to which point in time the database will be recovered. It is used simply to select from which backup the data will be restored (Restore Until Time). Note: No Recovery is the default selection in the Recovery Types section of the Oracle Restore Options tab. Be sure to select one of the other Recovery Types if you want to recover your database after restoring it.
Restore Manager
Restore From Backup Tag Option

When you select the Restore From Backup Tag option, you specify the tag that was used during backup to indicate which backup sessions to restore. The tag is the logical name assigned to a particular backup (for example, Monday Morning Backup). Note: No Recovery is the default selection in the Recovery Types section of the Oracle Restore Options tab. Ensure that you select one of the other Recovery Types if you want to recover your database after restoring it.
Until the End of Logs Option

When you select the Until the End of Logs option, the agent restores and recovers databases and database objects automatically, in one operation, if you also select the Put Restored Object(s) Online After Recovery option. When the restore and recovery is complete, the agent then opens the database. Important! If you select the Until the End of Logs option, do not include the control files in the restore unless it is missing or corrupted. If you include the control files in the restore, the agent recovers the database using the restored control files. As a result, all transactions made in the database that occurred after the last transaction recorded in the restored backup files are lost.
Restore Views
For any type of restore, you will use the default restore view on the Restore Manager. The Restore by File System view displays a tree of the hosts backed up by CA ARCserve Backup. To run a restore, expand the host to display databases and objects, and then select the specific databases or objects you want to restore. The databases displayed are from the most recent backup sessions. Note: The Restore by Session and Restore by Backup Media views are not supported for Agent for Oracle session restores. If you select the Restore by Media method, the session is skipped and the job will fail. You should refer to the CA ARCserve Backup Activity log to determine the exact cause.
Restore Databases and Database Objects

To restore a complete database backed up offline or online Note: Before starting the Restore Manager, be sure to start CA ARCserve Backup. 1. 2. Open the Restore Manager, select the Source tab, and then select the Restore by File System view. Expand the Linux Agent, and then expand the Oracle host under the Linux Agent.
Restore Manager
3. 4. 5.
Select the database you want to restore, or select the database objects to restore. Select the Destination tab, and expand the Linux Agent. Click the plus sign to the left of the Oracle SID under the Linux Agent. The Login dialog opens. If you did not click the plus sign to the left of the Oracle SID and you clicked directly on Oracle SID instead, you must enter the Oracle User Name and Password on the Oracle Options tab. These two fields are mandatory. In addition, since the Use RMAN catalog (Recommended) option is checked by default, you must enter the Owner Name and Owner Password of the RMAN catalog, unless the box is unchecked. If information from one of the mandatory fields is missing during the registration of the job, a dialog will display allowing you to enter the missing information. If you do not enter the missing information, the job will not be registered.
6. 7.
Enter the system user name and password and click OK. Click the plus sign to the left of the Oracle database you want to restore. The database Login dialog opens.
8.
Enter the Oracle dba user name and password and click OK. Note: Be sure that the Oracle user name and password you use to connect to Oracle has the permission to connect to Oracle using the as sysdba clause. You must be able to connect with and without this clause.
9.
To set restore options, select the Source tab and then click the Oracle Options tab: You can select the following Restore Options: Note: You can choose any combination of the options.
If you want RMAN to speed up the restore process when there are numerous tapes involved, choose the Number of Channels (Streams) option. Select more than one channel and RMAN will accept this value as the maximum number of channels to use during the restore. If you want to restore using the latest available backup, choose the Restore From Latest Backup option. If you want to restore a backup with a specific date and time, select the Restore From Backup Made On option. Note that RMAN will perform the operation on files up to, but not including, the specified time. If you want to restore a backup with a tag you used during the backup process, select Restore From Backup Tag option. If the archived redo logs are damaged or were removed as a result of a previous backup that used the Purge Log option, select one of the options (except Do Not Restore, which is the default) in the Archived Logs Selection section of the Advanced Oracle Options tab. This overwrites the archived redo logs.
Restore Manager
Note: If your archived redo log files are not lost or corrupted, generally you should not overwrite them. By keeping the archived redo logs, you can recover your database to the latest usable version that existed before your system or database failed.
If you want to restore the control files, you must select the Include Control File option on the Advanced Oracle Option tab. Note: Restore control files only when necessary, such as when they are missing or corrupted.
In addition to the Restore Options, you can select these Recovery Options:
If you do not want to perform a recovery after restoring the data, select the No Recovery option. Note: This option is checked automatically.
If you want to recover the database as closely as possible to the present time, select the Until the End of Logs option. If you want your database objects to be available as soon as recovery is complete, select the Put Restored Object(s) Online After Recovery option.
Note: For more information about other recovery types, see Restore Manager (see page 46). 10. Click Submit. The Submit Job dialog opens. 11. Schedule the job to run now or at a later time. Click OK to submit the job. The job is submitted. You can monitor job in the Job Status Manager. When the job is completed, the database objects are restored to the Oracle server. For instructions on recovering the Oracle database, see Database Recovery (see page 56). For more information about submitting restore jobs, see the Administration Guide.
Restore Archived Logs and Control Files

If your control files or archived log files have been lost or corrupted, you can restore them by selecting them on the Source tab of the Restore Manager when you configure a restore. Important! If you selected the Purge Logs after Backup option during backup, you must select one of the Archived Logs options (except Do Not Restore) on the Advanced Oracle Restore Options tab to ensure that RMAN triggers the restore of the required logs. If you do not select one of the Archived Logs options, the recovery phase will not function properly since the necessary logs may be missing. If you are using Oracle 9i and above, however, RMAN automatically restores the needed archived logs when you select one of the Recovery options.
Restore Manager
If your archived redo log files are not damaged, generally you should not include them in a restore. By keeping the archived redo log, you can restore your database to the latest usable version that existed before your system or database failed. If you select the Until the End of Logs option when you configure a restore, do not include the control files in the restore unless missing or corrupted. If you include the control files in the restore, the agent recovers the database using the restored control files. As a result, all transactions made in the database that occurred after the last transaction recorded in the restored backup files are lost.
Restore Parameter File

You can restore parameter files to a specific version using the Restore Manager. To restore a specific version of a parameter file 1. 2. 3. Select the parameter file you want to restore (such as, orapwfile). Click the Recovery Point button at the top of the Source tab. At the resulting dialog, select the exact version of the parameter file you want to restore. Click OK. Parameter files are the only type of database objects that you can restore to a specific version. Restoring your parameter files this way uses the CA ARCserve Backup agent directly and does not involve RMAN. Note: If the SQLNET.AUTHENTICATION_SERVICES option (set to "none") is in the init.ora file for any instance that you intend to backup and restore, you should comment it out before attempting to restore the orapwfile (included in the PARAMETER-FILES). Leaving it as it is prevents further sysdba database connections, and prevents normal management activities (such as recovery, shut down, and start up).
Restore Point-in-Time
To restore a database or tablespace to a point-in-time, follow the procedures to restore a complete database and the associated archive log files. For the appropriate procedure, see the different restore and recovery procedures in this guide. For more information about restoring or recovering the database or tablespace to a point-in-time, see the Oracle documentation. Note: The Until the End of Logs option, which automatically recovers a database after it has been restored, does not support point-in-time recoveries. If you want to perform a point-in-time recovery, you must perform the recovery steps manually.
Restore Manager
Recovery Manager (RMAN) and Restoring a Database to Another Host

To restore a database to another host using RMAN directly

You must have installed the RMAN catalog in a separate database, not in the source or destination database. Define and use a catalog with RMAN for both the backup and restore operations. Restore the whole database.
Note: The scenario used in the following procedure assumes that the database backed up from <host1> will be restored to <host2>, and that the database name will be preserved. It also assumes that the directory structure of the original and destination hosts are different. In addition, this scenario assumes you are using Oracle 8.
Restore a Database to Another Host Using RMAN

You can restore a database to another host using RMAN. To restore a database to another host using RMAN 1. Enter the following commands to obtain the db_id value (database ID) of the database you want to restore from the RMAN catalog:
sqlplus <rman user>/<rman password>@<rman service> SQL> select db_key, db_id, bs_key, recid, stamp, backup_type, start_time, status from rc_backup_set;
2. 3.
Identify the db_id value corresponding to the database you want to restore. Enter the following command to determine the file number and location of each data file in the source database:
SVRMGR> select file#, name from v$data file;
4. 5. 6. 7.
Copy the init<$ORACLE_SID>.ora file from $ORACLE_HOME/dbs on <host1> to <host2>. Edit the $ORACLE_HOME/dbs/init<$ORACLE_SID>.ora and adjust all paths to reflect the new directory structure on <host2>. Perform SQL*Net configure to ensure that the RMAN catalog is visible from both databases installed on <host1> and <host2>. Set up the Oracle password file on <host2> by entering the following command:
orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=kernel.
8.
Enter the following command to start the destination database with the nomount option:
SVRMGR> startup nomount pfile=$ORACLE_HOME/dbs/init<$ORACLE_SID>.ora
Restore Manager
9.
Enter the following commands to restore the control file: Note: You will need the db_id you obtained in Step 2.
rman rcvcat <rman username>/<rman password>@<rman service> RMAN> set dbid=<source database db_id value> RMAN> connect target <username>/<password>; RMAN> run { RMAN> allocate channel dev1 type 'sbt_tape'; RMAN> restore controlfile; RMAN> release channel dev1; RMAN> }
10. Enter the following command to mount the destination database:

SVRMGR> alter database mount;
11. Determine the new locations for each data file within the RMAN script using the locations you determined in Step 3. 12. Enter the following commands to restore the database using the new locations you determined in Step 11:
rman target <username>/<password> rcvcat <rman username>/<rman password>@<rman service> RMAN> run { RMAN> allocate channel dev1 type 'sbt_tape'; RMAN> set newname for data file 1 to '<new path>' RMAN> set newname for data file 2 to '<new path>' ... RMAN> restore database; RMAN> switch data file all; RMAN> release channel dev1;
13. Enter the following command to recover the database using the restored control files:
SVRMGR> recover database using backup controlfile until cancel;
14. Enter the following command to open the database using the resetlogs option:
SVRMGR> alter database open resetlogs;
Database Recovery
15. If the error ORA-00344: unable to re-create online log %s occurs: a. Enter the following commands to rename each online redo log:
SVRMGR> alter database rename file <online redo log #1 path> to <online redo log #1 new path>; ... SVRMGR> alter database rename file <online redo log #n path> to <onlne redo log #n new path>;
b.
Enter the following command to open the database:

SVRMGR> alter database open resetlogs;
Database Recovery
After restoring a database or database objects to the server, you must recover them. You can recover the database or database objects automatically using the Restore Manager or you can perform a manual recovery using the Oracle Server Manager Console. The following sections provide information and instructions for each of these methods.
Restore Manager Recovery

You can use the Restore Manager to restore and recover databases in one operation, automatically, by selecting one of these recovery options when you configure a restore job:

Until the End of Logs Until SCN (Whole DB Only) Until Log Sequence Number (Whole DB Only) Until Time (Whole DB Only)
Perform a Database Recovery

To recover the database or database objects using the Restore Manager, follow these steps: 1. 2. 3. 4. 5. Start CA ARCserve Backup. Open the Restore Manager and select the Restore by File System view. On the Source tab, expand the Linux Agent. Expand the Oracle host under the Linux Agent. Select the database or database objects you want to restore and recover. Note: To perform a complete media recovery of the database, you must restore all required archive log files.
Database Recovery
6. 7.
Select the Destination tab and expand the Linux Agent. Click the plus sign next to the Oracle host under the Linux Agent. The Login dialog opens.
8.
Enter the system user name and password, and click OK. The Oracle host expands.
9.
Click the plus sign next to the Oracle database you want to restore. The database Login dialog opens.
10. Enter the Oracle dba user name and password and click OK. Note: Be sure that the Oracle user name and password you use to connect to Oracle has the permission to connect to Oracle using the as sysdba clause. You must be able to connect with and without this clause. 11. Select the Source tab, click the Oracle Options tab, and then select one of the recovery options. 12. Click Submit on the toolbar. The Submit Job dialog opens. 13. Schedule the job to run now or at a later time. Click OK. The job is submitted. You can monitor job in the Job Status Manager. The agent automatically recovers the files after all the files have been restored.
Files the Agent Cannot Recover

When you use one of the Recovery Type options, the Agent for Oracle cannot recover the following files:

Corrupted or missing online redo logs Corrupted or missing data files that were not backed up by the agent Corrupted or missing control files that were not backed up by the agent Corrupted or missing archive logs that were not backed up by the agent Files belonging to a database running in the no archive log mode
Database Recovery
Oracle Constraints on Recovery Operations

The following Oracle constraints affect the recovery operations you can perform on a database:

When recovering data files and old control files, you must recover the entire database. You cannot perform a data file level recovery. When performing a full database recovery and some tablespaces are already offline prior to the restore operation, they will not be recovered automatically. You must recover data files manually before putting them back online. After you perform a point-in-time recovery or restore old control files, the redo logs can no longer recover data files restored from previous backups. Consequently, you must open the database with the resetlogs option. You must also run a full backup as soon as possible.
Manual Recovery
You can manually recover a complete database when the control files have been lost or become corrupted. The following section provides the details for performing this type of database recovery.
Recover Databases with Lost or Corrupted Control Files

If a control file has been lost or corrupted, you must first shut down the database and recover the control files before recovering the database. To shut down the database, recover the control files, and then recover the database, follow these steps: 1. Shut down the database by entering the following command at the SVRMGR or SQL*Plus prompt:
SHUTDOWN;
2.
At the appropriate prompt, start and mount the database and begin the recovery process.
At the SVRMGR prompt, enter the following command:

CONNECT INTERNAL; STARTUP MOUNT; RECOVER DATABASE USING BACKUP CONTROLFILE;
At the SQL*Plus prompt enter, enter the following command:

CONNECT SYSTEM/SYSTEM_PASSWORD AS SYSDBA; STARTUP MOUNT; RECOVER DATABASE USING BACKUP CONTROLFILE;
Database Recovery
3.
Oracle prompts you to enter the log file names. Oracle first looks for the archive log files and automatically supplies the correct names for those that exist. If Oracle cannot find the necessary archive log files, you must manually apply the online redo logs it needs. When you apply the online redo logs manually, you must supply the full path and file name. If you enter an incorrect log, re-enter the command:
RECOVER DATABASE USING BACKUP CONTROLFILE;
Supply the correct online redo log file name at the prompt. Continue this procedure until Oracle has applied all logs successfully. 4. Enter the following command at the SVRMGR or SQL*Plus prompt to bring the database back online and reset the logs:
ALTER DATABASE OPEN RESETLOGS;
5. 6.
Go to the directory where the archived redo logs are stored and delete all of the log files. If any tablespaces are still offline, enter the following command at the SVRMGR or SQL*Plus prompt to bring them back online:
ALTER TABLESPACE TABLESPACE_NAME ONLINE;
7.
If you are using RMAN to recover your complete database with backed up control files, resynchronize the database information in RMAN to reflect the newly recovered database. To resynchronize the database information, follow these steps: a. b. Login as oracle. Enter the following command to set oracle SID to the recovered database SID:
ORACLE_SID=database SID
c.
Enter the following commands to complete the process:

rman target dbuser/ dbuserpassword rcvcat catowner/catowner password@rman service name reset database
where:

dbuser is the user with dba privileges for the recovered database. dbuserpassword is the dbuser password. catowner is the Oracle user name of the Oracle Recovery Manager catalog owner. rman service name is the name of the service used to access the database where the rman catalog is installed.
Restore and Recovery Limitations
Recover from Offline Full Backups

If you backed up your database in offline mode, you will use the same process to recover it as if you had backed up the database in online mode. This is because the offline backup actually puts the database in a quiescent state, which means that the database is still online (although you cannot access it or process transactions).
Restore and Recovery Limitations

The following are restore and recovery limitations:

The online redo logs are not backed up; consequently, they cannot be restored. If any users are logged into the database when a restore job is scheduled to begin, the job fails if you are restoring either a system tablespace or a tablespace containing rollback segments. To avoid this, set the ORACLE_SHUTDOWN_TYPE variable to immediate in the /opt/CA/ABcmagt /agent.cfg file. The Catalog database SID should not be duplicated or shared with any other SID name. CA ARCserve Backup does not support restoring multiple, encrypted, Oracle RMAN sessions in a single restore job. You must restore encrypted Oracle RMAN backup sessions as individual restore jobs. CA ARCserve Backup does not support restore of old Oracle agent sessions using RMAN agent. If the restore job is submitted from Oracle RMAN command line, the job cant be rescheduled. That is, when you right-click the job "Ready/Hold/Run Now/Modify/Reschedule" will be grey in the job queue option.
Appendix A: Locating Directories and Files

This section contains the following topics: Agent Directory Locations (see page 61) Agent File Locations (see page 61)
Agent Directory Locations

The following directories are located under the home directory of the agent:

data--Internal data (Release Specific info) lib--Runtime Libraries logs--Log files nls--Messages files rman_scripts--Scripts automatically created by the agent
Agent File Locations

The following files are located in the home directory of the agent:

ca_auth--the program used to automatically register the user@host with CA ARCserve Backup ca_backup--the program used to submit backup jobs ca_restore--the program used to submit restore jobs ckyorn--the program used to read user information while performing setup instance.cfg--the file where all of the instances are listed at setup time libobk.so.1--the library to link Oracle with (SBT 1 | 32 bits) libobk.so.2--the library to link Oracle with (SBT 1 | 64 bits) libobk.so.2.64_IA64--the library link to Oracle with (Itanium support) libobk.so.2.64_AMD64--the library link to Oracle with (AMD Opteron support) oraclebr--the program used to run the browser oragentd--the program that is called by the common agent to perform the job orasetup--the script used to perform setup of the agent sbt.cfg--the parameter file created while performing setup
Appendix A: Locating Directories and Files 61
Agent File Locations
Agent Files Under Data Directory

The RELVERSION file, which stores the CA ARCserve Backup build number that the agent was built against, is stored under the Data directory.
Agent Files Under Logs Directory

The following log files are located under the Logs directory:

ca_backup.log--logs the output of the latest ca_backup command ca_restore.log--logs the output of the latest ca_restore command oragentd_<jobid>.log--logs the agents activity oraclebr.log--logs the browsers activity
Appendix B: Troubleshooting
This section contains the following topics: Assign Alias Name (see page 63) RMAN script back up for multiple channels fails (see page 63) Tips (see page 64) Messages (see page 64) RMAN Messages (see page 69)
Assign Alias Name

Symptom: The Linux Oracle Agent node with alias name is very long. Solution: You can also back up your Linux Oracle Agent node with alias name. For example, if the node name is long and you want to use a different name for it in backup manager perform the following steps before you can successfully do a backup and restore. To change host name 1. In the sbt.cfg file on your Linux Oracle Agent computer,
SBT_SOURCE_NAME=alias SBT_ORIGINAL_CLIENT_HOST=alias
where Alias is the name you specify for the Oracle Agent node in CA ARCserve Backup Manager SBT_SOURCE_NAME is the name which you used in Backup manager for the U/L Oracle agent node to do the backup. SBT_ORIGINAL_CLIENT_HOST is the node name which was used in backup and restore process. 2. Save the change and run caagent update the node name.
RMAN script back up for multiple channels fails

Symptom: RMAN script back up with multiple channels fails.
Appendix B: Troubleshooting 63
Tips
Solution: While performing multi-channel backup, the data at the receiving end maybe blocked by other channels for a long time causing the connection timeout between the agent and CA ARCserve Backup server, resulting in error E8522. To avoid this error, you must increase the timeout value (by default it is 20 minutes). To know more about how to set the timeout value, double-click on error E8522 from the activity log to get more information.
Tips
The following is a list of tips for the Agent for Oracle:
If the database you want to back up is not listed in the CA ARCserve Backup Source tab, check the instance.cfg file. For every database instance handled by the agent, there should be an entry for it in the instance.cfg file. This file is in the agent home directory. If you have trouble browsing a database, check the Oracle Browser Log (oraclebr.log) for possible errors. Also, make sure that the values corresponding to ORACLE_SID and ORACLE_HOME in the agent/instance.cfg file are set properly. We recommend there be only one RMAN catalog database for a local area network. If you are using RMAN, every host on which the agent is running should have a properly configured tnsnames.ora, Oracle Transparent Network Substrate configuration file. This file is in the $ORACLE_HOME/network /admin directory. The backup sessions you select to restore must have been successfully completed backup jobs. Do not attempt to restore a cancelled or failed backup job. If a job fails, always check the following logs for possible reasons for the failure:

oragentd_<job id>.log CA ARCserve Activity log The Oracle RMAN log ($ORACLE_BASE/admin/SID/udump/sbtio.log)
Messages
This section explains the most common messages for the agent on the Linux platform.
Backup or Restore Failed

Reason: There can be a number of reasons for backup or restore to fail.
Messages
Action: Check the agent log file, which is located in the agent/logs directory. For more information about backup operations, see your Oracle manual. If a previous backup job has failed, it may have left the source tablespaces in backup mode. To put the tablespace in normal mode, enter the following command at the SQL*Plus prompt:
ALTER TABLESPACE "tablespace_name" END BACKUP
No Oracle Server Icon

Reason: The agent is not installed or is not configured. Action: Install the agent. Check instance.cfg in the agent home directory.
Oracle - (209) ORA-01219. E8606

Oracle - (209) ORA-01219: database not open: queries allowed on fixed tables/views only. E8606 - Failed to enumerate databases. Reason: A backup of a mounted, but unopened Oracle server was attempted. Action: Open the Oracle server.
Shutdown Failure_E9900
Database not available for desired operation. E9900 Oracle: Instance shut down failure. Cant shut down the instance. Reason: Trying to perform a backup job and the agent cannot shut down the database. Action: Shut down the database and resubmit the backup job.
Messages
Fail to Connect to Oracle DBAgent

ERROR: Fail to connect to Oracle DBAgent with Browsing mode: return [24]. Database not available for desired operation. Reason: You are trying to perform an online backup job of an offline database. Action: Startup (mount and open) the database and resubmit the backup job.
!getOracleState()_Error_E9900
!get OracleState():olog()failed. Ida-rc=1033 Reason: ORA-01033:ORACLE initialization or shutdown in progress. DSA Connect Agent(): Cannot determine state of instance hpdb. ERROR: Fail to connect to Oracle DBAgent with Browsing mode:return[24]. E9900 Oracle: database not available for desired operation. Reason: You are trying to perform an online backup when the database was started with nomount or mount option. Action: The database must be in an open state for a successful backup job. Open the database and resubmit the backup job.
ConnecttoServer_ORA-01017_Cannot Log on
ConnecttoServer(): olog() failed.lda-return-code=1017 Reason:ORA-01017: invalid username/password; logon denied Cannot log on with given username/password. Reason: You submitted an online backup job with the wrong password. Action: Resubmit the job with the correct username and password.
Messages
OBK-5607_OBK-5629_OBK-5621_RMAN-6088
OBK-5607 Error accessing internal tables. OBK-5629 Error while executing select thread #, seq # from V$thread.OBK-504 SQL error ORA-01403 no data found. OBK-5621 file not belong to target database anymore target database information is out of sync. RMAN-6088 Data file copy not found or out of sync with catalog. Reason: The database instance name has the ./ character in its name. Action:
Check the instance name by using the following command:

select * from v$thread;
Change the instance name to one different from the database name or recreate the control files.
If you are using the svrmgr utility, drop the tablespace and recreate it with the full path name.
ORA-12223_ORA-12500
ORA-12223: TNS: internal limit restriction exceeded. ORA-12500 TNS: listener failed to start a dedicated server process Reason: Too many Transparent Network Substrate (TNS) connections open simultaneously. Action: Split the backup job into multiple jobs, with each job containing several tablespaces. The first job must include the system tablespace and the last backup job must include the archive log and the control files.
Messages
linux_user@hostname not validated

linux_user@hostname not validated in authentication server Reason: The CA ARCserve Backup user equivalency was not created, or if you're running Red Hat 6.1, you may have a bad information structure in the /etc/hosts file. Action: Check if you have properly created your CA ARCserve Backup user equivalency; check whether your /etc/hosts file has the following information structure:
host_ip_address localhost.localdomain local_host host name
IP Address of host localhost_oraclebr:fatal:relocation error

127.0.0.1 localhost.localdomain
IP address of host localhost.localdomain localhost hostname oraclebr: fatal: relocation error: file <...>/libclntsh.so: symbol slpmprodstab: referenced symbol not found Reason: This is an Oracle bug. Action: Either get a patch from Oracle or follow these steps: 1. 2. 3. 4. Logon as the oracle user. Shut down the database. Edit the $ORACLE_HOME/bin/genclntsh script. Comment out the following line:
ar d $LIBCOMMON sorapt.o
5. 6.
Regenerate the shared library (libclntsh.so) by running genclntsh. Restart the database.
RMAN Messages
ORA-19565:BACKUP_TAPE_IO_SLAVES not enabled

ORA-19565: BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices Reason: You are attempting to generate more than one copy for your backup. Action: Enable the BACKUP_TAPE_IO_SLAVES option in either your init<sid>.ora or SPFILE file when generating more than once copy of your backup.
RMAN Messages
This section contains common Recovery Manager (RMAN) messages. Note: For more information about RMAN messages, see the Oracle documentation.
Allocate Command Error

Allocate Command Error
RMAN-00571:================================================= RMAN-00569: ========= ERROR MESSAGE STACK FOLLOWS========== RMAN-00571:================================================= RMAN-03007: retryable error occurred during execution of command: allocate RMAN-07004: unhandled exception during command execution on channel dev1 RMAN-10035: exception raised in RPC: ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-19557: device error, device type: SBT_TAPE, device name: ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer Additional information: 4110 ORA-19511: SBT error = 4110, errno = 0, BACKUP_DIR environment variable is not set RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE. DEVICEALLOCATE
RMAN Messages
Reason: Oracle link to libobk library does not exist or failed. Action: Either relink Oracle to your libobk library or create a softlink by entering:
In-s $CAORA_HOME/libobk.so.1.32 $ORACLE_HOME/lib/libobk.so.
Unable to run ARCHIVELOG Mode

Symptom: When I try to expand a database, it does not expand and oraclebr.log says that the database is not running in ARCHIVELOG mode. How do I fix this? Solution: Set the database to run in ARCHIVELOG, as documented in the agent guide.
RMAN Exits With an Error during Backup or Restore

Symptom: When I try to run a backup or restore with RMAN, RMAN exits with an error right away. What should I do? Solution: Try the following steps only if you are performing a manual RMAN job: Note: If you used Restore Manager to start RMAN, these steps are performed automatically for you. Ensure that you have created the caroot equivalency with CA ARCserve Backup for the user who runs RMAN.
RMAN Messages
RMAN Job Exits with Agent Error

Symptom: My RMAN job exited and I got an error saying that the agent has not been started. How do I correct this? Solution: If the job stays inactive in the CA ARCserve Backup job queue for more than the number of minutes specified by the SBT_TIMEOUT parameter in sbt.cfg (because the tapes are not available, for instance), then RMAN will time out. Increase the SBT_TIMEOUT to accommodate your environment.
Until End of Logs Option Does Not Work

Symptom: For some reason, the Until End of Logs option does not work. How do I get it to work? Solution: Make sure that you have restored all the necessary archive logs. If it still does not work, try to perform a manual recovery on the restored files.
Backup or Restore Fails

Symptom: When I submit a backup or restore job from CA ARCserve Backup, it fails and there is no log produced for oragentd. How can I get the job to run? Solution: The agent has probably not been started. Check the common agent log (caagentd.log) for possible errors. If this log does not show anything special, make sure that the LD_LIBRARY_PATH, SHLIB_PATH, or LIBPATH entries in agent.cfg contain the right directories. If everything seems to be correct, consult the other CA ARCserve Backup logs for errors.
RMAN Messages
Too Many oragentd_<job id> Log Files are Accumulating

Symptom: I have too many oragentd_<job id>.log files accumulating in the Logs directory. Is there a way to clean it up? Solution: After completing a backup or restore operation, the oragentd process checks the value of the DAYS_ORAGENTD_LOGS_RETAINED parameter in agent.cfg of the common agent and deletes log files older than the number of days specified. To have a more frequent clean up, change this value and run the caagent update command (as root user). The default value is 30 days.
Oracle Permission Errors During Restore Operation

Symptom: While trying to perform a restore operation with the Until End of Logs option enabled, I get Oracle permission errors. How can I prevent the errors? Solution: Ensure that the Oracle user name and password you use to connect to Oracle through the Restore Manager has the permission to connect to Oracle using the as sysdba clause. You must be able to connect with and without this clause. You can verify your permissions by running the following commands:
sqlplus /nolog connect username/password as sysdba
If you do not have permission, ask the Oracle DBA to configure the security for you.
Restore Oracle Data Files in a Different Directory

Symptom: How do I perform a CA ARCserve Backup GUI restore operation to restore the Oracle data files in a different directory? Solution: You cannot do this. Although it is possible to restore a database to a different node, the whole directory structure where the database will be restored must be identical to the one on the source node.
RMAN Messages
Agent Fails with Oracle Password is Missing in the Job Message

Symptom: I am trying to run a backup or restore job, and the agent fails with the error Oracle password is missing in the job. How can I fix this? Solution: Make sure that the password is entered in the proper field in the Oracle Options tab.
Error Messages While Trying to Run Concurrent Backups on the Same Database
Symptom: I get error messages when I try to run concurrent backups on the same database. Should this happen? Solution: Yes. It is normal. Parallel operations that are handling the same Oracle objects at the same time are not supported. Symptom: The performance of the restore operation is slow. How can I speed it up? Solution: The shared memory apportioned between the child and the oragentd parent process uses a multi-buffering queue to parallelize as much of the transferred data as possible during the restore. The default number of blocks is 80. You can increase the number of blocks and speed up restore operations by editing the agent.cfg file in the common agent directory. Assign the new value to CA_ENV_NUM_OF_REST_BUFF, then uncomment this variable and make it active with the command caagent update. If you find that increasing the number of blocks does not help, you may want to try decreasing them instead. In some circumstances and on some platforms (such as OSF), reducing the number of blocks actually helped increase the performance. You will need to test different values to see what works for your particular situation.
Appendix C: Configuring the agent.cfg and sbt.cfg Files

This section contains the following topics: The agent.cfg Configuration File (see page 75) The sbt.cfg Parameter File (see page 77) Set the NLS_LANG Parameter (see page 83)
The agent.cfg Configuration File

The agent configuration file, agent.cfg, is located in the Common Agent home directory, and supplies the default information used when running orasetup for each sub-agent (Backup and Client Agent) installed on your system. It also contains the Oracle home directory, the user name and password of the Oracle Recovery Manager, and NLS_LANG and NLS_DATE_FORMAT information. Note: You must reload the agent using the caagent update command after changing the agent.cfg file. The following is a sample of the contents of the agent.cfg file:
[46] # Oracle Agent NAME Oracle Agent VERSION 15.0 HOME <Oracle Agent home directory> ENV CAS_ENV_ORACLE_AGENT_HOME=<Oracle Agent home directory> #ENV CA_ENV_NUM_OF_REST_BUFF= ENV DAYS_ORAGENTD_LOGS_RETAINED=30 ENV ORACLE_SHUTDOWN_TYPE=immediate #ENV NLS_LANG=american ENV NLS_DATE_FORMAT=MM/DD/YYYY/HH24:MI:SS ENV LD_LIBRARY_PATH=/usr/lib:<Oracle Agent home directory>:<Oracle Agent home directory>/lib:/opt/CA/ABcmagt:/usr/local/CAlib:$LD_LIBRARY_PATH BROWSER oraclebr AGENT oragentd
The CA_ENV_NUM_OF_REST_BUFF parameter lets you modify performance for restore operations. Since optimal values may vary depending on environments and host loads, modify this parameter with care.
Appendix C: Configuring the agent.cfg and sbt.cfg Files 75
The agent.cfg Configuration File
If you want to modify the number of days that the agent keeps the agent logs before it automatically deletes them, update the DAYS_ORAGENTD_LOGS _RETAINED variable. If you do not want to have the log files deleted automatically, enter 0. You should not manually change the settings for any of the Recovery Manager home directories listed in the agent.cfg file. Instead, to change these settings, rerun the orasetup program, enter the new information, and re-register it. You can also use the configuration file to select the type of shutdown Oracle will perform when an offline operation is required on an Oracle database. The supported values are normal, immediate, and abort. You should not enable the Debug option manually in the agent.cfg file. unless instructed to do so by a CA Technologies Customer Support representative. More information: Set the NLS_LANG Parameter (see page 83)
Enable Debug Option

You can enable the debug option using the following procedure: To enable the Debug option 1. Open the agent.cfg file (located in /opt/CA/ABcmagt) in an editor and add the following line:
ENV CA_ENV_DEBUG_LEVEL=4 ENV SBT_DEBUG=1
2.
Reload the agent using the caagent update command.
Note: You should not enable the Debug option, if necessary.
The sbt.cfg Parameter File
Restore Old Backup to an Alternate Location

You can restore the database objects like data files, parameter files, control files, and archive logs that were backed up using earlier versions, to an alternate location. To use this functionality, add the following parameter to the agent.cfg file:
ORA_RESTORE_DEST_DIR
Example: ENV ORA_RESTORE_DEST_DIR=/home/oracle/mydirectory Note: To restore the database objects to it's original location, you must remove or comment out the ORA_RESTORE_DEST_DIR parameter in the agent.cfg file.

After you create the initial sbt.cfg file, it is placed in the agent home directory. This file includes the following parameters:

SBT_HOST <host name>--Name of the host where the desired CA ARCserve Backup server runs. SBT_DATA_MOVER--Data mover value moves all the backed up data to a local data mover. Note: Ensure you run the orasetup script to reconfigure this parameter, instead of changing the value manually.
SBT_SOURCE_NAME--Sets the agent node name which is registered in the CA ARCserve Backup server. Note: If the node name registered in CA ARCserve Backup server is same as the agent node hostname, do not set this parameter.
SBT_ORIGINAL_CLIENT_HOST <host name>--When restoring data from one host to another, this parameter specifies the name of the original client host.
SBT_USERNAME <user name>--Name of a Linux user who can connect to the host where the Agent for Oracle runs. SBT_PASSWORD <password>--Password for the Linux user who can connect to the host where the agent runs. This value is encrypted using the cas_encr program. SBT_TIMEOUT <number of minutes>--Number of minutes that the Oracle Recovery Manager waits for the agent to be started before timing out. SBT_DESTGROUP <device group name>--Name of the CA ARCserve Backup destination device group to use for a backup operation. When this is not specified, any available device group is used. Note: This is a backup parameter only.
SBT_DESTTAPE <tape name>--Name of the CA ARCserve Backup destination media name to use for a backup operation. When not specified, any available media is used. Note: This is a backup parameter only.
SBT_MEDIAPOOL <media pool name>--Name of the CA ARCserve Backup destination media pool to use for a backup operation. By default, none is specified and no media pool is used. Note: This is a backup parameter only.
SBT_LOGFILE <log file path>--Records activities during the backup job to the specified filename. SBT_LOGDETAIL <summary | all>--Specifies whether a summary or all activity of the job should be logged in the file specified by the SBT_LOGFILE parameter. SBT_SNMP <true | false>--Indicates whether to use the SNMP alert option by the CA ARCserve Backup logger. The default value is 'false'. SBT_TNG <true | false>--Indicates whether to use the CA-Unicenter alert option. The default value is 'false'. SBT_EMAIL <email address>--Sends a copy of the Activity Log to the specified email address. The default is none. SBT_PRINTER <printer name>--Sends a copy of the Activity Log to the specified printer. The printer must be set up in the $BAB_HOME/config/caloggerd.cfg configuration file. The default is no printer.
SBT_EJECT <true | false>--Indicates whether the tape should be ejected at the end of the backup operation. The default is 'false'. Note: This is a backup parameter only.
SBT_TAPEMETHOD <append | owritesameblank | owritesameblankany | owritesameanyblank>--Method that determines how the job should handle the media:

append--Adds the session after the last one on the media. This is the default value. owritesameblank--Tries to use the media specified as the SBT_DESTTAPE parameter. If it cannot be used, tries to use a blank media. owritesameblankany--Tries to use the media specified as the SBT_DESTTAPE parameter. If it cannot be used, tries to use a blank media. If none is available, uses any tape. owritesameanyblank--Tries to use the media specified as the SBT_DESTTAPE parameter. If it cannot be used, tries to use any other tape. If none is available, tries to use a blank media.
Note: This parameter requires the SBT_DESTTAPE or SBT_DESTTAPESUN...SBT_DESTTAPESAT parameters to be set. This is a backup parameter only.
SBT_SPANTAPEMETHOD <owritesameblank | owritesameblankany | owritesameanyblank>--Method that determines how the job should handle the media in case of tape spanning:
owritesameblank--Tries to use the media specified as the SBT_DESTTAPE parameter. If it cannot be used, tries to use a blank media. This is the default value. owritesameblankany--Tries to use the media specified as the SBT_DESTTAPE parameter. If it cannot be used, tries to use a blank media. If none is available, uses any tape. owritesameanyblank--Tries to use the media specified as the SBT_DESTTAPE parameter. If it cannot be used, tries to use any other tape. If none is available, tries to use a blank media.
Note: This is a backup parameter only.
SBT_TAPETIMEOUT <number of minutes>--Number of minutes allowed for mounting a media before the job times out. The default value is 5 minutes. SBT_SPANTAPETIMEOUT <number of minutes>--Number of minutes allowed for mounting a media in case of a tape spanning situation before the job times out. The default value is infinite. SBT_DAYOFWEEK <true | false>--Indicates if the destination tape or media pool defined as values for SBT_DESTTAPESUN...SBT_DESTTAPESAT and SBT_MEDIAPOOLSUN...SBT_MEDIAPOOLSAT should be used instead of the default values specified for SBT_DESTTAPE and SBT_MEDIAPOOL. Note: This is a backup parameter only.
SBT_DESTTAPESUN <tape name>--Name of the media to use if the job runs on a Sunday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_DESTTAPEMON <tape name>--Name of the media to use if the job runs on a Monday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_DESTTAPETUE <tape name>--Name of the media to use if the job runs on a Tuesday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_DESTTAPEWED <tape name>--Name of the media to use if the job runs on a Wednesday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_DESTTAPETHU <tape name>--Name of the media to use if the job runs on a Thursday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_DESTTAPEFRI <tape name>--Name of the media to use if the job runs on a Friday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_DESTTAPESAT <tape name>--Name of the media to use if the job runs on a Saturday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_DESTTAPE value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLSUN <media pool name>--Name of the media pool to use if the job runs on a Sunday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLMON <media pool name>--Name of the media pool to use if the job runs on a Monday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLTUE <media pool name>--Name of the media pool to use if the job runs on a Tuesday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLWED <media pool name>--Name of the media pool to use if the job runs on a Wednesday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLTHU <media pool name>--Name of the media pool to use if the job runs on a Thursday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLFRI <media pool name>--Name of the media pool to use if the job runs on a Friday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_MEDIAPOOLSAT <media pool name>--Name of the media pool to use if the job runs on a Saturday and the SBT_DAYOFWEEK parameter is TRUE. If this is not specified, the SBT_MEDIAPOOL value applies. Note: This is a backup parameter only.
SBT_NB_BLOCKS <number of memory blocks>--Number of blocks of shared memory the SBT interface uses to exchange data with the agent. This is a tuning parameter and should normally not be modified. The default value provided is 50 blocks. SBT_APPEND_BACKUP_CMDLINE <command line arguments>--Arguments and values to append to the ca_backup command line generated by the SBT interface to submit a backup job. This is a generic way of providing parameters that are not supported by the SBT interface. SBT_APPEND_RESTORE_CMDLINE <command line arguments>--Arguments and values to append to the ca_restore command line generated by the SBT interface to submit a restore job. This is a generic way of providing parameters that are not supported by the SBT interface. Note: You can also define a parameter as an environment variable and as a parameter set by the send command in a RMAN script (for Oracle 9i, and 10g). To set a parameter in a RMAN script, enter the following:
run { allocate channel dev1 type 'sbt_tape'; send "SBT_HOST=myhost"; send "SBT_USERNAME=oracle"; send "SBT_PASSWORD=nobodyknows"; ... }
If you set a value through a send command in RMAN, this value overrides any value specified in the sbt.cfg file or the equivalent environment variable. If you set a value as an environment variable, it overrides the equivalent value specified in the sbt.cfg file.
Set the NLS_LANG Parameter
Set the NLS_LANG Parameter

When the CA ARCserve Backup Agent for Oracle calls the SQL*Plus to get the JPN datafile name from the oracle database. Sometimes it gives garbage characters "???.dbf" and the ARCserve database fails to catalog the tablespace name.The Agent fails to catalog the tablespace when the client character set is unable to identify the character set of the oracle databases. You can avoid this by setting the NLS_LANG variable before performing a backup or restore operation, since the commented NLS_LANG is written to the agent.cfg file of the Agent. You must also uncomment the NLS_LANG parameter and set the value and then restart the common agent to perform the backup and restore operations as shown in the following examples: Example 1 After you configure the Agent by running the orasetup script, the following line appears in the agent.cfg file:
#ENV NLS_LANG=American
To enable this parameter, you should uncomment it by changing the content after =. Now set the value of your choice and run the caagent update to sync the content with the common agent. Example 2 To set the NLS_LANG parameter for Oracle in JAPANESE environment 1. 2. Select the Oracle server character setting using the SQL*Plus, and ensure that the server character is using AL32UTF8. You can then add the following setting to the Agent.cfg file for the Agent.
NLS_LANG=AMERICAN_AMERICA.AL32UTF8
3.
Now call the caagent update to refresh the setting. The parameter is set.
More information: The agent.cfg Configuration File (see page 75)
Glossary
control file A control file is a file where a database records the status of the physical structures within the database. datafile A datafile is an operating system file that describes the physical structure of a database. glossary entry Oracle RMAN (Oracle Recovery Manager) is an Oracle application that lets you back up, restore, and recover Oracle databases from a disaster. For more information about how to use Oracle RMAN, see the Oracle web site. index An index is a database component that lets you retrieve data from the database. Oracle RAC Oracle RAC (Real Application Cluster) is an application that provides you with clustering and high-availability protection for Oracle database environments. For more information about using Oracle RAC, see the Oracle web site. redo log A redo log is a file where Oracle databases records changes to the database. schema object A database schema defines the structure of a database. tablespace A tablespace is a database component where database management objects are stored.
Glossary 85
Index
A
archived online redo log files understanding 31 ARCHIVELOG mode compared to NOARCHIVELOG mode 19 must set Oracle to 31 automatic archiving, enabling 17
F
files agent cannot recover 57
I
installing the agent post-installation tasks 15 instance.cfg 20
B
backing up defined 29 limitations 44 multistreaming 41 number of channels (streams) option 41 number of channels (streams) option, procedure 41 offline mode 33 one or more databases online 38 Recovery Manager, manually 43 Recovery Manager, using scripts with 43 strategies 29 using RMAN scripts in the agent, procedure 42
L
libobk.so library files relinking in LINUX 26 Log Files oragentd.log 64
M
multiple databases viewing 31 working with 31 multistreaming description 11
C
CA ARCserve Backup 11 CA ARCserve Backup Agent for Oracle features 11 introduction 11 understanding 12 catalog, create 22 catowner 43 catownerpassword 43 configuring the agent 20 control files, defined 30 cross platform database backups, description 11
N
NOARCHIVELOG mode 19 number of channels (streams) option example 41 understanding 41
O
online redo log files defined 30 understanding 31 Oracle Server control files 30 data files 30 online redo log files 30 organization 30 parameter files 30 recovery area 30 tablespaces 30 orasetup, running 20
D
data files defined 30 dbuser 43 dbuserpassword 43
Index 87
P
parameter files, defined 30 PFILE 18 post-installation tasks automatic archiving, enabling 17 configuring the agent 20 listed 15 orasetup 20 Recovery Manager (RMAN) 24, 33
R
recovering database objects using Restore Manager 58 databases with lost or corrupted control files 58 defined 45 explained 56 files that cannot be recovered 57 limitations 60 manual recovery 58 offline full backups 60 Oracle restraints 58 with Restore Manager 56 recovery area, defined 30 Recovery Manager add CA ARCserve Backup user equivalency 24, 33 backing up manually 43 catalog 22 description 11 libobk.so library files 25 relinking for 24, 33 restoring a database to another host using 54 rman database 43 sbt interfaces 24 sbt.cfg parameter file 77 using 32 using scripts in 43 restore by backup media 50 restore by file system 50 restore by session 50 restoring archive log files 52 basic concepts 45 complete databases 50 control file restores, understanding 52 control files 52 database objects 50
database to another host using Recovery Manager 54 databases backed up offline 50 databases backed up online 50 defined 45 limitations 60 options 48, 49, 50 restore by file system 50 restore views 50 RMAN, see Recovery Manager 32 to point-in-time 53 types 46 until the end of logs option 50 what can be restored 45 RMAN, see Recovery Manager 32
S
sbt.cfg 20 SIDs 20
T
tablespaces defined 30 Troubleshooting Tips oratab file 64 tnsnames.ora 64
U
Until the end of logs option defined 50

CA ARCserve Backup para Linux Agente para Oracle

Uploaded by

Copyright:

Available Formats

CA ARCserve Backup para Linux Agente para Oracle

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CA ARCserve Backup para Linux Agente para Oracle

Uploaded by

Copyright:

Available Formats

CA ARCserve Backup for Linux

Agent for Oracle Guide

CA Technologies Product References

Chapter 2: Installing the Agent

Chapter 3: Backing Up Data

Chapter 4: Restoring and Recovering Data

Appendix A: Locating Directories and Files

8 Agent for Oracle Guide

Appendix C: Configuring the agent.cfg and sbt.cfg Files

Chapter 1: Introducing the Agent for Oracle

Chapter 1: Introducing the Agent for Oracle 11

12 Agent for Oracle Guide

Chapter 2: Installing the Agent

The Agent in a RAC Environment

Chapter 2: Installing the Agent 13

Install the Agent

Install the Agent

14 Agent for Oracle Guide

Perform Post-Installation Tasks

Perform Post-Installation Tasks

Chapter 2: Installing the Agent 15

Perform Post-Installation Tasks

Check ARCHIVELOG Mode

16 Agent for Oracle Guide

Perform Post-Installation Tasks

Start ARCHIVELOG Mode

Chapter 2: Installing the Agent 17

Perform Post-Installation Tasks

Enable Automatic Archiving for Oracle Installation Using PFILE

Some of the log parameters include the following:

18 Agent for Oracle Guide

Perform Post-Installation Tasks

Enable Automatic Archiving for Oracle Installation Using SPFILE

ARCHIVELOG to NOARCHIVELOG Mode Comparison

Mode ARCHIVELOG mode

Chapter 2: Installing the Agent 19

Perform Post-Installation Tasks

Mode NOARCHIVELOG mode

Configure the Agent

20 Agent for Oracle Guide

Perform Post-Installation Tasks

Chapter 2: Installing the Agent 21

Perform Post-Installation Tasks

Create an RMAN Catalog

22 Agent for Oracle Guide

Perform Post-Installation Tasks

Chapter 2: Installing the Agent 23

Post-Installation Tasks Required for Recovery Manager

Connect to the catalog database and target database of RMAN.

Post-Installation Tasks Required for Recovery Manager

Use library files by performing one of these actions:

The SBT 1.1 and SBT 2.0 Interfaces

24 Agent for Oracle Guide

Post-Installation Tasks Required for Recovery Manager

How the SBT Library Uses the sbt.cfg Parameter File

How the SBT Inteface Uses libobk Library Files

Chapter 2: Installing the Agent 25

Post-Installation Tasks Required for Recovery Manager

Some other considerations include: