Introduction To System Landscape
When we design the landspace for a SAP Project, generally we prefer to have same platform for Development, Test and Production system.
- Hardware (32-bit or 64-Bit and also IA64, X64, or Unix 64 Bit platforms)
- Operating System
- R3 Kernel
This helps, system administrators to identify system related problems causes functional problems.
For example, if a 64-Bit Kernel for Netweaver 700 on Windows/Oracle causes a problem, you cannot simulate it on your Test system if it is a 32 Bit platform.
Also you have to make sure that the kernel patch levels are all same on all systems.
System Copy Experience with 64-bit to 32-bit
Recently, one of our Customer asked us to copy Production System to their Test System.
Here is the systems environments:
Production System (Source System)
|Hardware||64-bit Intel Xeon (x64)|
|Operating System||64-bit Windows 2003 R2 SP1|
|Database||Oracle 10.2.0.2 64-bit|
|SAP Kernel||700 64-bit PL 133|
Test System (Target System)
|Hardware||32-bit Intel Xeon (x86)|
|Operating System||32-bit Windows 2003 R2 SP1|
|Database||Oracle 10.2.0.2 32-bit|
|SAP Kernel||700 32-bit PL 72|
Here is the brief procedure. For details, please download System Copy Guides from http://service.sap.com/instguides
- Stop Production System to copy files or use a recent online/offline backup to copy database files from production to test syste
- Run "alter database backup controlfile to trace" on source database to get control file creation script.
- Generate new cntrl.sql and run on target system with modified paths
- Recover if backup is online via "recover datbase using backup controlfile until cancel;"
- After recovery shutdown database on target with "shutdown immediate". Do not use "shutdown abort"
- cd ORACLE_HOME/rdbms/admin on target system with
- sqplus "/as sysdba"
- SQLPLUS> startup upgrade
- SQLPLUS> @utilrp.sql
- SQLPLUS> shutdown immediate
- SQLPLUS> startup
- SQLPLUS> @utlrp.sq
- If databaase scheme name is different from SAPSR3 on both systems, then you've to change dbs_ora_schema environment value to the one on Source System.
- If schema name is other than SAPSR3, than you have to re-configure OPS$ me. For this please check the reference section which gives OPS$ mechanism notes.
- Check connection with "R3trans -d"
- Start SAP System and apply, post-copy procedures.
Hope it helps you to understand that it is not necessary to use R3load Procedure even platforms are different in bit level.
Note 050088 - Creating OPS$ users on Windows NT/Oracle
Note 361641 - Creating OPS$ users on UNIX
Taken from http://www.basisconsultan.com.