Show TOC

RAC with BR*ToolsLocate this document in the navigation structure

Use

You can manage up to 32 parallel instances of the Oracle Real Application Cluster (RAC) with BR*Tools. You normally start these tools only on the dedicated database (DDB) instance, as defined in SAP Note 621293 Information published on SAP site.

Prerequisites
  • Check the requirements in Oracle Real Application Cluster (RAC).

  • The necessary BR*Tools executables must exist on the DDB instance host in directory /usr/sap/<SAPSID>/SYS/exe/run.

  • A common spfile must exist on the DDB instance host in directory <ORACLE_HOME>/dbs (UNIX) or <ORACLE_HOME>\database (Windows).

    spfile.ora contains all instance-independent and all instance-dependent parameters for all Oracle instances. For more information, see SAP Note 830982 Information published on SAP site.

  • The backup devices (tape units or hard disks) are normally connected locally to the DDB instance host.

  • The init<DBSID>.sap profile parameter parallel_instances contains all Oracle instances, including the local instance. As of Oracle 11g, this profile is located in <SAPDATA_HOME>/sapprof (UNIX) or <SAPDATA_HOME>\sapprof (Windows).

  • The log directories for BR*Tools saparch, sapbackup, sapcheck, and sapreorg are all on shared file systems.

  • The Oracle archive directory, oraarch, is on a shared file system or on an ASM disk group

  • The following directories are on a shared file system:

    • Oracle profile directory:

      UNIX: <ORACLE_HOME>/dbs

      Windows: <ORACLE_HOME>\database

    • Trace directory: saptrace

    • Audit directory: ~/rdbms/audit

    • The entire <ORACLE_HOME> directory, if possible

  • The Oracle SQL*Net configuration corresponds to the recommendations in SAP Note 830982 Information published on SAP site.

  • For special considerations regarding Oracle RAC on Oracle Automatic Storage Management (ASM), see SAP Note 1598594 Information published on SAP site.

  • UNIX only: BR*Tools requires as standard an Oracle password file for the remote connection. For more information, see SAP Note 131610 Information published on SAP site.

Activities

If you have set up the user SYSTEM correctly, it now has the authorization to start and stop the database instances remotely. Therefore, you can call BRBACKUP and BRARCHIVE as usual, for example:

brbackup -u system/<password>...

brarchive -u system/<password>...