How to System Copy in SAP Business Intelligence (BI SYSTEM) System Landscapes?

The below post explain how the System Copy in SAP Business Intelligence System Landscapes in detail.

1. Take the backup f the production system (Source)
2. Pre-Steps on the target system (The tables/ Data that need to be restored after a system copy)
3. Clean the database (SAPDATA1, SAPDATA2,…………..)

SQL> Select username from DBA_USER;

SQL> Select table_name from dba_tables where owner = ‘OPS$willsys99\NWADM’;

4. Restore the database from backup /or physical copy of the datafiles (SAPDATA1, SAPDATA2…………..)
5. Generate control file (Alter database backup control file to trace)

A trace file is generated in saptrace directory

Rename the file to control.sql (Change the SID and path name of datafiles accordingly)

6. Remove the entries before “startup nomount” and after “Characteristics WE8DEC’

Run Control file on the target system

7. Run “Oradbusr.sql” to setup permissions on the database to create OPS$USERS
8. Up to 4.6c SAPR3 is the owner of the database.
9. up to ECC5.0 SAP<SID> is the owner of the database.
10. From Netweaver 04S (WebAS 7.0) on wards SAPSR3 is the owner of the database for ABAP. SAPSR3DB is for the JAVA system.

System Copy (For BI System)

Mechanism:

1. User i.e. work process connects to the database as user “OPS$<Hostname>\SIDADM to get SAPSR3’s password.
2. SAPSR3 is the schema user whose password stores in table SAPUSER which is owned by OPS$<hostname>\SIDADM

Note: OPS$ mechanism provides a means to connect to the database without any password i.e. user with prefix OPS$. The OS user is created in the database with prefix OPS$(OS Username).

The connection is only possible when …

SQL> select count * from dba_table where owner = ‘SAPSR3’;

SQL> select bname from SAPSR3.USR02;

Remote_OS_Authenticate = True

3. The Process gets the password and disconnects the session.
4. Process relogins to the database with user SAPSR3 who owns the complete SAP database.
5. Now the user can access the complete SAP Schema.
6. When the user log in with userid/ password/ mandt/ language it goes to the table USR02 (Internal security of SAP) to validate users.

Note: If any of the 1-5 fails then R3Trans -d results (0012) snote : 400241

SAPSR3 password resides in two tables.

1. DBA_USERS
2. SAPUSR TABLE

SAP recommends to change the schema user password using BRTOOLS/ SAPDBA.

If it is manual we need to change in two tables.

SQL> Insert into table ‘OPS$<hostname>/SIDADM’.SAPUSER values

SQL> Alter user SAPSR3 identified by “New password”

When you insert password it is alphanumeric(It will be in the encrypted format after restart)

Goto > Tcode SECATT

Test [ ] create

Description [ ]

Component [BC]

[SAVE]

Also See: What is SAP Router? and How to Configure SAP Router?