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.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.
5.System Licensing:Request a permanent license through OSS. Install the new license using the operating system saplicense command or through Tx SLICENSE.
6.System Patching (Optional):
·Install the SPAM update and support packages to the latest levels or to match existing instances in the same landscape. Use appropriate OSS notes to ensure the correct groupings of support packages are imported and to avoid problems (i.e. note# 672651 and note# 598767). Follow step #3 in note 598767 to prevent SQL Error 229.
·Note:Keep the R/3 SPAM and Support Pack versions the same across instances of the same landscape.
7.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.
8.Client Administration:Depending on the source system, some steps may not be required. However, all steps should be reviewed for applicability.
·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.
9.Solution Manager