SAP Basis Tech Supports

Symptom

The SAP scope of delivery contains components (for example, the requisite log) that are based on Oracle but do not meet the name and structure conventions of standard SAP databases. Therefore, you cannot use BR*Tools to save or restore these databases, or to otherwise manage them.
Since the safety strategies of standard SAP systems are mostly based on BR*Tools, it is useful to integrate these SAP components into them.
Other terms

BRARCHIVE, BRBACKUP, BRCONNECT, BRRECOVER, BRRESTORE, BRSPACE, BRTOOLS
Reason and Prerequisites

Installation Information
This solution supports the following components only:
* Requisite catalog
* MDM component
* IPC component
* Redwood Cronacle
* IXOS Archiving (as of BR*Tools 7.00 patch 22)
* Vertex Taxing (as of BR*Tools 7.00 patch 22)
* Ingeneo (as of BR*Tools 7.00 patch 28)
* Oblicore (as of BR*Tools 7.00 patch 28)
* Visiprise (as of BR*Tools 7.00 patch 30)
Important:
——–
This note does not apply to SAPJ2EE and Enterprise Portal Oracle databases. For information about the installation of BR*Tools on Java databases prior to Version 6.40 SR1, see Note 668604, section 3, post installation: “Install dba tools manually”. As of this version, BR*Tools are completely installed automatically by SAPInst for Java databases.
Solution

The BR*Tools are largely independent of the name and structure conventions of standard SAP databases. You must create only a few additional directories and database tables to run it. The new directories and BR executables should include the same operating system user as the database files. Under this user, the system should also execute the backups.
1. Creating the directories with BR executables
————————————————
Create any new directory, and define the environment variable SAPEXE that points to the directory. Download the latest versions of BR*Tools (brarchive, brbackup, brconnect, brrecover, brrestore, brspace, and brtools) from SAP Service Marketplace, unpack and copy them to the new directory (see Note 12741). Add the directory to the PATH environment variable.
2. Creating the log directory of the BR*Tools
—————————————————
Create any new directory, and define the environment variable SAPDATA_HOME that points to the directory. Create the following subdirectories in this directory:
saparch, sapbackup, sapcheck, and sapreorg.
3. Creating a tablespace for the database user SAPR3
————————————————————-
sqlplus /nolog
SQL> connect / as sysdba
SQL> create tablespace psapdba datafile ‘‘ size 20m;
where: – any file name
4. Creating the database user SAPR3
—————————————
SQL> create user sapr3 identified by default tablespace
psapdba;
SQL> grant connect, resource to sapr3;
5. Creating the tables SDBAH and SDBAD
—————————————
SQL> create table sapr3.sdbah
(beg varchar2(14) default ‘ ‘ not null,
funct varchar2(3) default ‘ ‘ not null,
sysid varchar2(8) default ‘ ‘ not null,
obj varchar2(16) default ‘ ‘ not null,
rc varchar2(4) default ‘0000′ not null,
ende varchar2(14) default ‘ ‘ not null,
actid varchar2(16) default ‘ ‘ not null,
line varchar2(254) default ‘ ‘ not null)
tablespace psapdba storage (initial 64K next 64K pctincrease 0
minextents 1 maxextents 100);
SQL> create table sapr3.sdbad
(beg varchar2(14) default ‘ ‘ not null,
funct varchar2(3) default ‘ ‘ not null,
sysid varchar2(8) default ‘ ‘ not null,
pos varchar2(4) default ‘0000′ not null,
line varchar2(254) default ‘ ‘ not null)
tablespace psapdba storage (initial 256K next 256K pctincrease 0
minextents 1 maxextents 100);
SQL> create unique index sapr3.sdbah__0 on sapr3.sdbah (beg, funct)
tablespace psapdba storage (initial 16K next 16K pctincrease 0
minextents 1 maxextents 100);
SQL> create unique index sapr3.sdbad__0 on sapr3.sdbad (beg, funct, pos)
tablespace psapdba storage (initial 64K next 64K pctincrease 0
minextents 1 maxextents 100);
6. Creating the backup profile init.sap
————————————————
Copy a backup profile init.sap from a standard SAP system to the directory $ORACLE_HOME/dbs (Unix) or %ORACLE_HOME%\database (Windows NT), and adjust the database-dependent and operating system-dependent parameters accordingly. (For additional information referring to the profile, see the online documentation for BR*Tools.)
The BR*Tools should then be executable. You normally use the database user SYSTEM to execute the backups, for example, brbackup -d disk -m all -u system/ -c.
Note 1:
———-
If you want to use the Oracle OPS$ mechanism to avoid entering the password in the command line, create the corresponding OPS$ user with SQLPLUS first:
sqlplus /nolog
SQL> connect / as sysdba
SQL> create user ops$ identified externally; and implement the SAPDBA role:
sqlplus /nolog @sapdba_role R3
You can then start BRBACKUP as follows:
brbackup -d disk -m all -u / -c
Note 2:
———
You may only use the BR*Tools for Oracle databases of SAP components.
Note 3:
———-
Do not create any MLICHECK or SAPLIKEY tables in the database.