Wednesday, October 22, 2008

System Copy with Oracle 10g from 64-bit to 32-bit on Windows E-mail Print PDF

Following procedure helps you to do a system copy from a 64-bit to 32-bit hardware with Windows/Oracle Platform.

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.

This includes,

  • Hardware (32-bit or 64-Bit and also IA64, X64, or Unix 64 Bit platforms)
  • Operating System
  • Database
  • 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

Environment

Recently, one of our Customer asked us to copy Production System to their Test System.

Here is the systems environments:

Production System (Source System)

Component
Version
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)

Component
Version
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

Procedure

Here is the brief procedure. For details, please download System Copy Guides from http://service.sap.com/instguides

  1. Stop Production System to copy files or use a recent online/offline backup to copy database files from production to test syste
  2. Run "alter database backup controlfile to trace" on source database to get control file creation script.
  3. Generate new cntrl.sql and run on target system with modified paths
  4. Recover if backup is online via "recover datbase using backup controlfile until cancel;"
  5. After recovery shutdown database on target with "shutdown immediate". Do not use "shutdown abort"
  6. cd ORACLE_HOME/rdbms/admin on target system with adm
  7. sqplus "/as sysdba"
  8. SQLPLUS> startup upgrade
  9. SQLPLUS> @utilrp.sql
  10. SQLPLUS> shutdown immediate
  11. SQLPLUS> startup
  12. SQLPLUS> @utlrp.sq
  13. 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.
  14. 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.
  15. Check connection with "R3trans -d"
  16. Start SAP System and apply, post-copy procedures.

That's it.

Hope it helps you to understand that it is not necessary to use R3load Procedure even platforms are different in bit level.

References

Note 050088 - Creating OPS$ users on Windows NT/Oracle

Note 361641 - Creating OPS$ users on UNIX


Taken from http://www.basisconsultan.com.

2 comments:

Dmitry said...

Best articles! But can you say more info at 16 step ?

What is "post-copy procedures" ?

Best regards.

Shruti Ramalingam said...

Thanks for the great information ,was looking for this information from long.Great blog SAP Basis Training in Chennai