Sunteți pe pagina 1din 24

HETEROGENEOUS SYSTEM COPY SCM5.

0
(NW7.0 SR3)
1.Technical data on source system
System ECC 6.0 PLM
System SID: S01
Host Name: dewall49
OS Level (oslevel s): Aix 5.3 (5300-07-03-0811)
JAVA full version (java fullversion): J2RE 1.4.2 IBM AIX 5L for PowerPC
(64 bit JVM.SAP 142SR1a + 88494.
DB: Oracle full Version: 10.2.0.2.0
FQDN: dewall49.ccss.capgemini.com
Stack: ABAP+JAVA
SAP File System (df g):
/Oracle
Total Size: 238GB Free: 31GB
/usr/sap
Database Size: (DB02)
42GB

Total size: 105GB Used: 63.GB

Oracle_Home: /oracle/S01/101_64

Disk Layout:

Total Size: 48GB Free: 20GB

Size: 2.92 GB

Free:

VG02 is Volume group for Oracle Database Installation.


VG01 is Volume group for SAP for /usr/sap.
50GB is size of HDD size.
Memory:
Physical Memory

Virtual Memory

JAVA:
Sidadm>java fullversion
Java JDK version 1.4.2 SAP142SR1a

JAVA Home
sidadm>echo $JAVA_HOME
/usr/java14_64

Software Component and Service Pack:


Kernel Version: 179

Increase The SAP Kernel to level of SR3.


ABAP

---------------------------------------------------------------------

Preparation
2. Need to find out System is on which SR level.
Note 789220 SP Level for NW Installation & Upgrade. Found that SR 3
is SPS 14.Source system is on SPS 13.
Reference Documentation
System Copy Guide based on NW 7.0 SR3.
Netweaver 7.0 SR3 Installation Guide based on DB2
Notes
Note
Note
note)
Note
Note
Note

1120872
888210

Hom./Het.System Copy SAP NetWeaver 7.0 SR3


NetWeaver 7.0/7.10: System copy (supplementary

789220
552464
1177833

SP Level for NW Installation & Upgrade


What is Big Endian / Little Endian? What Endian do I have?
DB6 specific R3szchk patches overview

Migration Key from SAP market Place:


http://service.sap.com/migrationkey

Installation
Installation number
Installation name

0020100427
BW in CCSS, Walldorf

Migration Key
Migration key
Expiration date

17efdeM50TH01eqtd1Q90Qm2
05.10.2009

Or use 1G5fdEM50TIIrBzjt6TE5Pae refer note 1120872

DVD List on Export


DVD No
Description
Location

51033511_1

NW 7.0/BS2005 SR3 Installation Master AIX 64bit /newCDs/sapcd/NW7.0

51033513_4/4 NW 7.0 SR3 SP14 Java bs SW Comp.1_4


Export DVDs created from source system

/newCDs/sapcd/NW7.0/51033513
/oracle/export

Based on Size of Oracle Database and compression of ratio 1:5


Assign 30% of used Database to free space in /export directory so Calculation is 19 GB
-Create Export Directory:
Logon as root
#cd /oracle
#mkdir export
#chown R biwadm: sapsys export
-Check source system consistency by SICK.

-Check Reorg jobs running as per snote 16083.


-Take Offline DB Backup using DB13.
-Take backup of following file system:
/usr/sap/<SAPSID>
/usr/sap/trans
<sapmnt>/<SAPSID>
Home directory of the user biwadm and orasid
For Example tar cf <file_system> | compress c > ARCHIVENAME.tar.Z

sap.tar.Z
/usr/sap/biw
/sapmnt,
Home directory of biwadm : /usr/sap/sapmnt/BIW/home/biwadm
Home directory of orabwi: /oracle/orabiw.

Upgrade Kernel
We have upgraded kernel 133 to the level of SR3. Standards copy procedure.
Download and Load r3szcheck utility:

Support Packages and Patches


Support Packages and Patches SAP NetWeaver SAP NETWEAVER SAP
NETWEAVER 7.0 Entry by Component Application Server ABAP
Copy R3LOAD, R3SZCHECK, R3LDCTL files to
/usr/sap/sapmnt/BIW/exe

No Prepare Phase on the source system.


Login using Administrative user in Client 100
Lock all Production users.
T.code SU10.Make sure all Admin or system and RFC users are not locked.
Check no canceled or Pending Update
T.code Sm13. Check canceled Updates

Check pending update

Set all released jobs from Released to Scheduled


T.code sm37

Select all jobs and Make change the status to Schedule.

10. Operation mode


Check Operation Mode Calendar. T.code sm63.

The display show that there is no Operation mode switch scheduled.

11. Logical system and client overview


As BW system has only one Master client in our case its 100. Goto T.code SCC4 and note down
Logical system BIWCLNT100. This is use ful incase you are changing SID. so you have to adapt
systems logical client using new sid.

SAP Note 184447 can be required here.

Delete QCM table.

The List empty so the there are no QCM tables available.


No Pending Incremental Conversion.
T.code ICNV.

Object waiting for Mass Data Processing


T.code SE14

Compare SAP DDIC and RDBMS DDIC


T.code DB02

There are many unknown object appearing in ABAP dictionary. This object are manly Temp
Objects /BIO/01
referred note 1139396 to drop this objects
Drop Temp.Objects
Run report from t.code se38

Note 1139396 - Temporary database objects in BW 7.X


As per notes all temp. Objects will be deleted with out checking that if they are in use by this
report.

Check Support Package Manager for any pending Update.


If there is any Upgrade pending in queue please finish it. If there is error in processing the
queue please get it rectified before starting export.
Check Transport Request
T.code SE09
Make sure that the tables TATGPC and TATGPCA are empty

6. generate DDL satatement


Generate SQL for

Export source system


Shutdown SAP Instance
Create Export dump using sapinst as follows.
Login as root user
set temp directory
export TMP=/oracle/tmp
export TEMP=/oracle/tmp
export TMPDIR=/oracle/tmp
2. C) open sapinst

/usr/sap/sapmnt/BIW/profile

Generated SQL statements are copied to following path and press OK to continue.

Start time : 20 March09 system time 14:20

Problem 1: At system time 18:20 on 20 March 2009

Observation : checked export_monitor.java.log found

checked SAPAPPL0_2.log
(EXP) ERROR: DbSlExeRead failed
rc = 103, table "/BIC/TZCS_SRGIO"
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(DB) INFO: disconnected from DB
This tables is in Data dictionary and not created in DB. Can be safely ignored.
Solution: SAPAPPL0_2.TSK file is edited to skip creation of this file in dump.
Opened with vi SAPAPPL0_2.TSK and changed err<->ok for this table;
Also During import, we need to take care of this object. I will make entry in negtab: is TPL file
so that even
it will not stop at error.

Note; The state file allows package states to be manually updated to restart failed R3load
processes.
export_state.properties in <inst_directory>
Example
if package processing failed and the package state has the value , the state can be set
to 0 and processing of the package is restarted.
n To restart package processing, set the package state from to 0.
n To skip package processing, set the package state from 0 or to +. (This is not
recommended, because it can cause inconsistent data files or database content.)
n If the package is currently being processed (the package state is ?), then any manual
modifications
of the package state are ignored. We dont have to do any change in this file

Estimated Time for export:


Export size: 10 GB
Start Time 20 March 14:20 20 March 18:20
= 4 Hours
Start 21 March 11:20 -- 23 March 11:49
= 20 min
Total Export estimated time is approx. 4:20 min
DB estimation (in MB):
ABAP
JAVA
Total

= 49539
= 4254
= 53793 MB

approx. 55 GB

Target DB estimated at 55 GB.

S-ar putea să vă placă și