Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 9760

Re: SAP Upgrade from SAP R/3 4.7 to ECC 6.0

$
0
0

Hi Bruno,

 

The upgrade involved different stages.  Our target server is different so we have to export our source DB and use the export to install R3 Enterprise 4.7 on  Win 2008 64bit (Oracle 11.2.3) on a migration server and did the upgrade from there.  We did not combine unicode conversion so we export it out again and install to the final server as unicode.

 

Original Server (Win 2003 32bit) - DB export

Migration Server (Win 2008 64bit) - Perform upgrade (via SUM) -> DB export

Final Server (Win 2008 64bit) - DB import (Unicode)

- For different servers, you may have to generate and install different SAP licenses

 

1. Take an export of your DB (DB EXPORT – ORA 9.2.0.4_WIN 32 bit)

- DVD used 51019679 to run DB export from the Original Server

 

2. Prepare a Migration Server for DB & OS UPGRADE – ORA 11.2.0.3_WIN 64 bit

- DVDs used:

51042334 (ORADMS 11.2.3)

51043312_11 (SAPINST)

51040088_13 (KERNEL)

51039412 (ORA_CLIENT)

51030724_1 (JAVA_IGS)

 

3. Patch Kernel, SPAM and Support Packages

Kernel to 640_EX2 NUC level 414

SPAM to level SAPKD62051

SAP_BASIS to level SAPKB62067

SAP_ABA to level SAPKA62067

ST-PI 2005_1_620 to level SAPKITLQG8

 

Please take note of the following SAP Notes before you do SPAM and SP import.

627246 - Error when you create new objects. ORA-02168

782140 - OCS: Known problems with Support Packages in Basis Rel. 6.20

447925 - OCS: Known problems with Support Packages in Basis Rel. 6.20

 

4. Pre-requisites for Release Upgrade using SUM

- Use Solution Manager’s Maintenance Optimizer (may have to patch the SolMan to latest version) to generate the XML stack

you may refer to http://scn.sap.com/docs/DOC-26893

- Download the patches from the XML stack generated.  Copy to the migration server

- If you are building DEV and QAS system out of the XML of your PRD, make sure you edit the XML file to contain info such as server name, SID and SP level.

- Prepare the following DVDs

51041988 SAP EHP3 FOR SAP NETWEAVER 7.0 Kernel 7.20 EXT

51041994 EHP6 FOR SAP ERP 6.0 Upgrade Export

51041940 Oracle Instant client 11.2.0.3

51041990 EHP6 Language DVD

SUM10SP09_4-20006676.SAR

 

5. Run SUM (Release Upgrade)

Refer to the guide: Update of SAP Systems Using Software Update Manager 1.0 SP09

Run SUM\STARTUP.BAT

Run SUM\sdt\exe\DSUGui.bat

 

6. Prepare for Unicode conversion

- if you decided to combine unicode conversion with the upgrade, you may have to do this before hand

- refer to the following documentations

http://scn.sap.com/docs/DOC-8864

1096903 - Tutorial: "Table splitting in SPUMG or SPUM

1051576 - Conversion of Single Code Page Systems to Unicode

996990 - Exception List for transactions SPUMG and SPUM4

 

7. Do a NUC DB Export

- SInce we did not choose to combine UC conversion with upgrade, we need to make another DB export and import it later as UC

- Run SWPM (51047249_SWPM1.0_7.1x) (SAPinst)

- Use the System Copy option

 

8. Final DB Import via System Copy

Prepare the Final Server and Do a Fresh Installation of ECC6 (Unicode) using DB import via System Copy

51042334 - ORADMS 11.2.3

51047217 - UC Kernel NW7.31

51047249 _ SWPM1.0_7.1x (SapInst)

 

9. Do post UC and System Copy Activities

- SAP License

- TMS Config

- Kernel DBTools Patches

- etc

 

 

Its a long procedure almost 45 hours end-to-end.  You may encounter errors along the way and have to raise OSS Messages.

 

Hope this helps.

 

Thanks,

 

Tony


Viewing all articles
Browse latest Browse all 9760

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>