Summary
This article describes how to backup multiple Oracle instances installed on a single server.
Resolution
In some cases, multiple Oracle instances have been installed on the same server and must be backed up using different job parameters, including the master server name or IP address, the media pool name, device cluster name, etc. RMAN jobs are initiated from the Oracle server (as opposed to non-RMAN jobs that are started from the DPX master server) and use a special configuration file containing job options that can be modified.
Sometimes, you may wish to use different control files for different Oracle instances to distinguish your backups. The default name for the control file is sbt11cfg.bex, and it is placed in the default directory (that is, the DPX root directory) during the installation of the interface to RMAN jobs. You can modify this file (specifying your desired options) and move it to a different location. In some cases, you must rename it using the Oracle instance name. DPX checks locations in a certain order and uses the file as soon as it finds it. The order of the locations that are searched can be found in sbtio.log, which is the Oracle MML log located in the directory under ORACLE_BASE. (It may be a different directory depending on the Oracle version.)
For Windows platforms, it is practical to put different configuration files with Oracle instance names in WINNT\system32. Different control files with the name of Oracle instances can be put in the ORACLE_HOME\dbs directory on Windows and UNIX platforms in case multiple Oracle instances are installed under the same ORACLE_HOME. The SSOBEX_CONFIG_FILE environment variable that points to the configuration file can be used on UNIX.