感谢jamesyen,主要是借鉴其方法和思路！


http://space.itpub.net/?uid-65240-action-viewspace-itemid-684307


SAP Homogenous System Copy Export/ImportMethod


R/3 ERP 2005 SR2, ECC 6.0 (Unicode)

Oracle 10.2,Windows Server 2003

Bye James Yen, Dec 20, 2007

Required materials

Documentation

·System Copy guide:System Copy for SAP Systems Based on NW 7.0 SR2 ABAP+Java.This guide is downloaded fromhttp://service.sap.com/instguides(under Installation and Upgrade Guides -> SAP Business Suite Familiy of Business Applications -> SAP ERP -> SAP ERP 6.0 -> Installation). Version 1.1 , Nov 07, 2007

·Solution Operation Guide for SAP ERP 6.0 – Support Release 2,This guide is downloaded fromhttp://service.sap.com/instguides(Installation and Upgrade Guides -> SAP Business Suite Familiy of Business Applications-> SAP ERP -> SAP ERP 6.0 -> Operation). Document Version 8.00 – September 25, 2007

·CriticalOSSNotes:(http://service.sap.com/notes)

970518 - Hom./Het.System Copy SAP NetWeaver 7.0 (2004s) SR2

723909 - Java VM settings for J2EE 6.40/7.0

551915 - R/3 won't start after database restore or database copy

931024 - FAQ: 64-bit platforms for Windows

146289 - Parameter Recommendations for 64-Bit SAP Kernel

088416 - Zero administration memory management as of 4.0A/Windows


Software

·J2SDK 1.4.2_15-x64- Java Development Kit

·51031678- Oracle 10.2 Installtion (NT\AMD64)

·51031725_2- Oracle 10.2.0.2 Patches (WIN_AIX_SOL\NT\AMD64)

·51032269- Java Component NW2004***2

·51033208_13 -ERP_2005_SR2_SAP_Installation_Master (IM_WINDOWS_X86_64)

·51033032_15 -NW_2004s_SR2_Kernel(KU_WINDOWS_X86_64)

·51033272 –Oracle Client (OCL_WINDOWS_X86_64)

·A directory on the target server, namedExport, to copy the source system files.

Technical Steps Overview

1.Technical preparations (source system)

2.Export the database (source system)

3.Copy export files from source to target system

4.Check the operating system and prepare target system.

5.Install ERP 2005 SR2 Central instance (target system)

6.Install Oracle 10.2 and Patch (target system)

7.Cont. Install ERP 2005 SR2 Central instance (target system)

8.Post-installation steps (target and source systems)


Technical preparations (source system)

·Plan ahead for required downtime. The source system will be shut down for several hours during the database export.

·Request a special backup of the system if necessary (i.e., newly upgraded, patched, etc.) prior to the export

·Perform. the steps as described in section 3.2, “Technical Preparations, Preparing the Source System” on pages 20-23 of theSystem Copy for SAP Systems Based on NW2004s SR2 ABAP(SysCopy_NW70SR2ABJA101007.pdf).

·This would be a good time to set/reset the DDIC andSAP* passwords of the source system or at least document their values. Also - ensure that the DDIC andSAP* user ID's are unlocked before you start the export.

Exporting the database (source system)

1.Stop theSAPinstance using the Microsoft Management Console, leave the database running.

2.Make sure that a Java Virtual Machine (JVM) is installed on the system. To determine if a JVM is installed on the system, open a command window on the server (source and target) and type the following command:java –version

If a JVM is not installed, download it from Sun and install it. This process was verified using JVM version build 1.4.2_15-x64.Note, SAPinst checks environment variable SAPINST_JRE_HOME for a valid Java runtime environment.If SAPINST_JRE_HOME is not found, SAPinst also checks JAVA_HOME.

3.Exporting the database, SAPinst performs the following steps:

·Creates the export directory structure with label files

·Creates database structure files (*STR)

·Updates database statistics

·Calculates the size of the target database(*EXT,DBSIZE.XML)

·Exports the database content

·Archives the SDM

·Archives application-specific file system content

4.As of NW04s,SAPINST is not installed permanently on the server. All runs ofSAPINST originate from the installation master cd-rom. Copy the installation master cd-rom to a local drive, not a mapped network drive. D:\CDs\51033208_13\BS_2005_SR2_SAP_Installation_Master\IM_WINDOWS_X86_64

5.Run theSAPINST.exe program to start the GUI. Use the following table to respond to the prompts fromSAPINST:

1.Run theSAPINST.exe program to start the GUI. Use the following table to respond to the prompts fromSAPINST:


Screen Name

Input

Welcome to SAP Installation Master

SAP ERP 2005 SR2 -> Additional Software Lifecycle Tasks -> System Copy -> Oracle -> Source System -> Central System -> Based on AS ABAP+JAVA -> Database Instance ExportNEXT

General Parameters

Select the profile directoryNEXT

Windows Domain

Select the domain model, typically Local Installation

OS User Passwords

Enter the password of the adm userNEXT

Export Location

Browse the system to select your database export locationNEXT

Parameter Summary

StartNEXT

Copying the export files to the target system

·Make sure there is sufficient disk space on the target system.

·Copy the entire export directory from the source system to the target system.

Installing a ERP 2005Central Instance (Target system)

Locate the fileSAPINST on the master installation cd-rom in
subdirectory 51032260_11_BS2005_SR2_Installation_Master_Windows_Server_on_IA32_32bit

·Double-click the fileSAPINSTto begin the installation. The installation files are extracted into subdirectoryc:\program files\sapinst_instdir\.

·TheSAPINST GUI starts. Use the following table for help on responses:


Installation Screen

Suggested Response

Main Installation Screen-> Choose Service

SAP Installation Master -> SAP ERP 2005 SR2 -> Additional Software Lifecycle Tasks -> System Copy -> Oracle -> TargetSystem -> Central System -> Based on AS ABAP and AS JAVA -> Central System InstallationNextè

Define Parameters -> Parameter Mode

Select CustomNextè

Software Package Request -> Java Component NW2004***2

D:\CDs\51032269Nextè

Java Development Kit

C:\j2sdk1.4.2_15_x64Nextè

General Parameters -> SAP System ID (SAPSID) and Instllation Deive and Unicode

SAP System ID (SAPSID) : PS1,Installation Drive: D:

Unicode System (recommended): checkedNextè

SAP System -> Master Password

Password for all users of this SAP system and ConfirmNextè

SAP System-> Windows Domain

Domain Model -> Local InstallationNextè

SAP System -> OS User Passwords

SAP System Administrator passwordand SAP System Service User Passowrd

Nextè

SAP System -> Database ->

Database Installation -> Installation Method

Select Standard System Copy/Migration (Load-based)Nextè

SAP System -> Database Parameters ->

Database IS (DBSID): PS1, Database Host: socw3s1xxxxNextè

Oracle -> Server Software

Oracle Software are not installed. Install Oracle software firstNextè

Install Oracle 10.2 Software

D:\CDs\51031678-oracle\NT\AMD64\sapserverNaNdNextè

(Keep SAPinstwindow opened without interrupt ECC 6.0 Installation)

(It will take 30-40 mins to install Oracle 10.2)

Apply Oracle 10.2.02 Patch

D:\CDs\51031725\DVD_ORACLE_10.2.0.2_Patches_WIN_AIX_SOL\NT\AMD64 (Specify Home Detail: Name: SID102 and Path D:\oracle\SID\102)

Nextè

Oracle -> Server Software

Select Oracle server software is installed, continue Oracle -> Server Software

Oracle -> Database System

Database Instance Parameters: DBHome, DB Server Version

Instance Memory: Instance Ram: 4063

Database Schema Parameters: ABAP Schema: SAPSID, JAVA Schema: SAPSIDDBNextè

Oracle -> Database System for OBR

Databse Server Drives: Drive for sapdataHome and Drive for Oracle Archive (oraarch): Select D: DriveNextè

Oracle -> Standard Database Users

Oracle Database Users: Password of sys and system, use defaultNextè

Oracle -> Listener Configuration

Oracle Listener Configuration: Select defaultNextè

SAP System -> Secure Store Settings

Secure Store Settings: Keep it defaultNextè

SAP System -> Central and SCS Instance

Enter the Central and SCS instance parameters: default is 00 and 01Nextè

SAP System -> Central and SCS Instance -> Service Ports

Enter the Central and SCS instance service ports: default is 3600, 3900 and 3901

Nextè

Media Browser -> Software Package Request

Enter the location of the export file from source System:

Migration Export: D:\CDs\exportNextè


SAP System -> Secure Store Information

Enter the required user information of Existing J2EE Engine

Administrator : j2ee_admin, password: xxxxxxxxxxNextè

SAP System -> SDM

Enter a password from source system for SDM Server ConnectionNextè

SAP System -> DDIC

Enter a password from source system for DDIC, Client 000Nextè

Media Browser -> Software Package Request

Enter the location of the UC Kernel NW2004***2 and Oracle client:

UC_Kernel _NW2004***2:D:\CDs\\51033032_15\KU_WINDOWS_X86_64

Oracle Client:D:\CDs\51033272\OCL_WINDOWS_X86_64Nextè

SAP System -> UnPack Archives

Select which Archives you want to uppack -> Select defaultNextè

Parameter Summary

Choose Start to Start with the values shown or select the parameters you want to change and choose ‘Revise’Startè

SAP System -> SAP Solution Manager

Enter the SAP Solution Manager KeyNextè

Task Progress

Execution of Service has been completed SuccessfullyOKè

·Installation runtime takes up to 5-6hours or more.

Post-installation activities (source system)

·Reschedule any cancelled background jobs(TxSM37)

·Update the operation mode timetable to the original status. (TxSM63)

Post-installation activities (target system)

1.Reboot the server and log in asadm.Check the Oracle environment setup is correct and Brtools is working.

2.StartSAPusing the Microsoft Management Console. Use standard R/3 troubleshooting procedures (check trace files, etc.) if theSAPsystem does not start up.

3.Log on to client 000 with an administrative account other thanSAP* or DDIC. If no other user accounts exist, log on to the system withSAP* or DDIC and create a new user account (TxSU01). Create the new user account with profilesSAP_ALL andSAP_NEW.
Note:You may have to create new company assignments in Tx SUCOMP first.

4.Purge Source System Data
Some data from the source system cannot be used by the target system. Purge this data as follows:

·Delete cancelled/finished jobs.RunTxSE38, report RSBTCDEL with optiondelete with forced modefor all users.

·Purge all entries in the following tables: TPFET, TPFHT, DDLOG, ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP and SDBAR (suggested to run “truncate table…” commands at the database level)

·In TxSM58, delete all entries in the system.

5.Transport Management System (TMS).

·Run TxSE06and choose the optionDatabase Copy. Answeryesto all of the prompts.

·RunTxSTMSand configure the Transport System. If this system is part of a multiple system landscape, use virtual systems as placeholders until the physical system is installed. When the physical system is installed, remove the virtual systems from the TMS landscape and configure the server in its place.

6.Initial Checks:Run the following transactions:

·TxSM28 (SICK)– Initial consistency check. Correct errors if any exist.

·TxSM50/51– Check processes. Document current kernel patch level.

·TxSM21– System log. Look for errors and correct as necessary. If you receive the errorIn table TCPDB, there are 0 entries, run report RSCPINST as directed in note# 42305. However, this should not be the case, as the source system would already contain TCPDB entries for Unicode.

·TxDB02– Check database consistency as soon as possible. Check the Database Recovery Model (should be “Full”) and, if necessary, change using SQL Enterprise Manager.

7.System Licensing:
Request a permanent license throughOSS. Install the new license using the operating systemsaplicensecommand or through TxSLICENSE.

8.System Patching (Optional):

·Install the SPAM update and support packages to the latest levels or to match existing instances in the same landscape.

9.RFCs:RunTxSM59and verify/adjust the RFC calls to point to the correct systems or delete outright. It is likely the RFC connection (type R/3) can be deleted.

10.Client Administration:Depending on the source system, some steps may not be required. However, all steps should be reviewed for applicability.

·Tx BDLS:Run this transaction to adjust remaining client specific data to the new logical systems created in BD54. (This job may take some time). Log on to the remaining client, run TxBDLS, specify the old logical system (CLNT), and the new, non-existent logical system (, and run. You’ll find that the new logical system has been created in the table TBDLS (use Tx BD54)

·Tx BD54:Create new logical systems as needed for new clients in the target system – format is CLNT. DO NOT delete source system clients as of yet.

·Tx SCC4:Create new clients and/or adjust the logical system names and settings of current clients to the new situation.

·Tx SCCL:If needed, perform. local client copies to the requirements of the target system.

11.Solution Manager

·If the newSAPinstance is connected to aSAPSolution Manager system, download and install the latest ST-PI and ST/A-PI plug-ins using Tx SAINT. Update the plug-in Support Packages to the latest levels.

·Keep the ST-PI and ST/A-PI versions and Support Package levels the same across instances of the same landscape.

·Additionally, configuration changes in RZ20 and RZ21 should be checked and reconfigured if needed.

12.Spooling:UseTxSPADto adjust output devices to the target system hostname. Next, run a consistency check of TemSe objects in TxSP12(TemSe Data Storage -> Consistency Check)

13.System Time Zone:If required, change the system time zone using TxSTZAC. Perform. this action in a client where modifications are allowed or use TxSCC4to temporarily change client settings to allow the time zone change.

14.Help:UseTxSR13to set up the R/3 documentation link. Point to the local documentation server or theSAPhelp portal:http://help.sap.com.

15.Profiles/Operation Modes

·Run TxRZ10to import profiles of the active server (Utilities menu). Change the profile parameters as appropriate. For now, set the default login client (login/system_client = xxx) in the instance profile.

·Run TxRZ04and recreate the desired operation modes with the target server profiles.

·Check/confirm the proper configuration of operation modes in TxSM63.

16.Other Configuration:

·OSS1:configure theOSSconnection parameters.

·SMLG:Check configuration and server assignment of logon groups.

·SM54 and SM55:Delete entries in tables TXCOM and THOSTS.

·DB13:Delete and recreate any jobs in the calendar.

·SUCOMP:Adjust the system for the proper company name(s) for the installation.


18.ABAP Loads:Use TxSGENto run a system generation to pre-compile the ABAP loads. Select the optionGenerate All Objects of Selected Software Components. At a minimum, select the componentsSAP_ABA,SAP_APPL,SAP_BASIS, andSAP_HR. Watch the Tablespace Free space.

19.Perform. a full backup of the target system.  

The system installation is complete. You can begin system configuration.