Agent for Oracle (Windows)

The following section provides information on support for the Agent for Oracle:

• Database files are excluded (skipped) from backups submitted through the Client Agent for Windows up to a limit of 2048 files. If your number of database files exceeds this limit, you must add a DWORD registry value called MaxFileFilter to make sure all database files are properly excluded from the backups made with the Client Agent for Windows:
• HKEY_LOCALMACHINE\SOFTWARE\ComputerAssociates\CA ARCserve Backup\Base\Task\Backup
• Value Name: MaxFileFilter
• Type: DWORD
• Value: Set to a value greater than the number of database files you wish to exclude. For example, if there are 3006 DB files, a value of 4096 ensures all database files are excluded from the backup.
• When performing a backup of Oracle objects with copies, such as the Oracle Tablespace or full database, the job fails if the BACKUP_TAPE_IO_SLAVES parameter is false. To set this parameter to true, perform the following steps:
  1. Open a sqlplus prompt.
  2. Enter the following command:
  3. alter system set backup_tape_io_slaves = true deferred
  3. Restart the database.
  4. Set the Number of Copies option to a value greater than 1.
  5. Submit the backup job.

  Note: You may also use the "show parameter backup_tape_io_slaves" command to check the value of the parameter.

• When you change the system time on the machine on which Oracle Server and the Agent for Oracle are installed, archive log backups fails.
• When performing a database restore job that fails, the job continues after the error only if you are restoring by session. If you are restoring by tree, subsequent sessions will not be restored because Restore by Tree packages all the sessions into a single node, while Restore by Session packages all sessions into different nodes.
• When performing an offline backup of an Oracle RAC9i database with RMAN options from the GUI, Arcserve Backup does not put the database into offline mode. To avoid this issue, consider the following:
  • Put the database into MOUNT status before performing offline backups.
  • Put the database into MOUNT status before performing full database backups without control file restore, system tablespace restores, or undo tablespace restore.
  • Put the database into NOMOUNT status before performing full database plus control file restores.
  • For user tablespace restores, do not perform anything.
• When submitting RMAN backup and restore jobs, please ensure that the user is in the Administrators Group on the Oracle Server machine.
• The Agent for Oracle (RMAN) does not support special characters used in passwords (for example, '@'). Backup jobs fail if used.
• This version of the Agent is case sensitive. If one modifies the previous job or loads a previous job script before upgrading the Agent from earlier versions to the current release, the Oracle database instance may appear twice; once as uppercase and once as lowercase. This issue affects only display, not performance.