SAP System Copy Guide, ECC 6.0, Oracle - Part (3)

SAP System -> Secure Store Information	Enter the required user information of Existing J2EE Engine Administrator : j2ee_admin, password: xxxxxxxxxx                            Next è
SAP System -> SDM	Enter a password from source system for SDM Server Connection     Next è
SAP System -> DDIC	Enter a password from source system for DDIC, Client 000                Next è
Media Browser -> Software Package Request	Enter the location of the UC Kernel NW2004sSR2 and Oracle client: UC_Kernel _NW2004sSR2:  D:\CDs\\51033032_15\KU_WINDOWS_X86_64 Oracle Client: D:\CDs\ 51033272\OCL_WINDOWS_X86_64            Next è
SAP System -> UnPack Archives	Select which Archives you want to uppack -> Select default                Next è
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 Key                                                   Next è
Task Progress	Execution of Service has been completed Successfully                          OK è

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

Post-installation activities (source system)

·       Reschedule any cancelled background jobs(Tx SM37)

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

Post-installation activities (target system)

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

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

3.     Log on to client 000 with an administrative account other than SAP* or DDIC. If no other user accounts exist, log on to the system with SAP* or DDIC and create a new user account (Tx SU01). Create the new user account with profiles SAP_ALL and SAP_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. Run Tx SE38, report RSBTCDEL with option delete with forced mode for 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 Tx SM58, delete all entries in the system.

5.     Transport Management System (TMS).

·       Run Tx SE06 and choose the option Database Copy. Answer yes to all of the prompts.

·       Run Tx STMS and 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:

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

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

·       Tx SM21 – System log. Look for errors and correct as necessary. If you receive the error In 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.

·       Tx DB02 – 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 through OSS. Install the new license using the operating system saplicense command or through Tx SLICENSE.

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: Run Tx SM59 and 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 Tx BDLS, 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 new SAP instance is connected to a SAP Solution 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: Use Tx SPAD to adjust output devices to the target system hostname. Next, run a consistency check of TemSe objects in Tx SP12 (TemSe Data Storage -> Consistency Check)

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

14.     Help: Use Tx SR13 to set up the R/3 documentation link. Point to the local documentation server or the SAP help portal: http://help.sap.com.

15.     Profiles/Operation Modes

·       Run Tx RZ10 to 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 Tx RZ04 and recreate the desired operation modes with the target server profiles.

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

16.     Other Configuration:

·       OSS1: configure the OSS connection 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 Tx SGEN to run a system generation to pre-compile the ABAP loads. Select the option Generate All Objects of Selected Software Components. At a minimum, select the components SAP_ABA, SAP_APPL, SAP_BASIS, and SAP_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.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/65240/viewspace-684310/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/65240/viewspace-684310/