on 07-08-2015 11:02 AM
Dear All
We have done homogeneous copy for our SAP ECC6.0 System.
Source System Details:
===================================================================
Operating System : MS Windows 2003 Enterprise 64 bit Version
Database : MS SQL 2005
Cluster : Windows Cluster with Three Application Servers(DIs)
Component Version: SAP ECC6.0
SAP_BASIS 700 0019 SAPKB70019 SAP Basis Component
SAP_ABA 700 0017 SAPKA70017 Cross-Application Component
PI_BASIS 2005_1_700 0017 SAPKIPYJ7H PI_BASIS 2005_1_700
ST-PI 2008_1_700 0008 SAPKITLRD8 SAP Solution Tools Plug-In
SAP_BW 700 0019 SAPKW70019 SAP NetWeaver BI 7.0
SAP_AP 700 0014 SAPKNA7014 SAP Application Platform
SAP_APPL 600 0014 SAPKH60014 Logistics and Accounting
SAP_HR 600 0028 SAPKE60028 Human Resources
EA-IPPE 400 0011 SAPKGPID11 SAP iPPE
EA-APPL 600 0011 SAPKGPAD11 SAP Enterprise Extension PLM,SCM, Financials
EA-DFPS 600 0011 SAPKGPDD11 SAP Enterprise Extension DefenseForces & Public Security
EA-FINSERV 600 0011 SAPKGPFD11 SAP Enterprise ExtensionFinancial Services
EA-GLTRADE 600 0011 SAPKGPGD11 SAP Enterprise ExtensionGlobal Trade
EA-HR 600 0024 SAPKGPHD24 SAP Enterprise Extension HR
EA-PS 600 0011 SAPKGPPD11 SAP Enterprise Extension PublicServices
EA-RETAIL 600 0011 SAPKGPRD11 SAP Enterprise ExtensionRetail
FINBASIS 600 0011 SAPK-60011INFINBASIS Fin. Basis
DMIS 2010_1_700 0010 SAPK-91710INDMIS DMIS 2010_1_700
ECC-DIMP 600 0011 SAPK-60011INECCDIMP DIMP
ERECRUIT 600 0011 SAPK-60011INERECRUIT E-Recruiting
FI-CA 600 0011 SAPK-60011INFICA FI-CA
FI-CAX 600 0011 SAPK-60011INFICAX FI-CA Extended
INSURANCE 600 0011 SAPK-60011ININSURANC SAP Insurance
IS-CWM 600 0011 SAPK-60011INISCWM Industry Solution CatchWeight Management
IS-H 600 0012 SAPK-60012INISH SAP Healthcare
IS-M 600 0011 SAPK-60011INISM SAP MEDIA
IS-OIL 600 0011 SAPK-60011INISOIL IS-OIL
IS-PS-CA 600 0011 SAPK-60011INISPSCA IS-PUBLIC SECTORCONTRACT ACCOUNTING
IS-UT 600 0011 SAPK-60011INISUT SAPUtilities/Telecommunication
LSOFE 600 0011 SAPK-60011INLSOFE SAP Learning SolutionFront-End
SEM-BW 600 0011 SAPKGS6011 SEM-BW: Strategic EnterpriseManagement
NMI_CONT 2006_1_700 0018 SAPK-61718INNMICONT NMIContent
ST-A/PI 01Q_700 0002 SAPKITAB7L Servicetools for otherApp./Netweaver 04
Kernel Version:
Kernel release 700
Compilation NT 5.2 3790 Ser
ABAP Load 1563
CUA load 30
Mode opt
Rsyn file
Database information:
DB client lib. SQL_Server_8.00
DB releases MSSQL 7.00.699 or
DBSL version 700.08
DBSL Patch Level 350
===================================================================
Target System Details:
SAP ECC6.0
Operating System : MS Windows 2012 R2 Std 64 bit Version
Database : MS SQL 2012
===================================================================
We performed the following steps for doing the homogeneous copy.
In Source System:
Step 1: Upgraded SP level of BASIS to 26
Step 2: Upgraded SP level of ABAP to 26
Step 3: Upgraded SP level of BW to 28
Step 4: Run SWPM and choose export system copy installation
Select the option of System Copy - Attach/Detach Method
And generate Export Files
Step 4: Detached the Data from Source
In Target System
Step 1: Installed Windows 2012 Operating System
Step 2: Installed SQL 2012
Step 3: Attached Database
Step 4: Run SWPM
System Copy Target Installation - Attach/Detach Method has been chosen.
Followed the screen instruction
Now the target system is up and running.
As per the above system environment, I need to know what are post installations steps to be performed.
Please help me to clarify the following queries also,
1. Do I require to copy the Profile parameter from Source to Target System after homogeneous copy?
If yes, Can you specify the procedure?
If no, Can you specify the recommended profile parameter?
2. Is it require to delete Transport Routes and configuration?
3. Is there anything performed in Database level?
4. What about all background jobs?
Please explain all post installation steps after homogeneous copy - attach/detach method.
Thanks
Sel
Hello Sel,
Please find post step after homogeneous system copy.
1. Cancel any production batch jobs:
a. Transaction SM37, enter job name, user “*”, and date range including the next day, job status “released” and click “execute”
b. Select the job, go to the Job menu and click “released->scheduled”
2. Delete Source System profiles and Import the correct SAP profiles
a. Transaction RZ10
b. Go to Utilities > Import Profiles > Of Active Servers
3. Delete Source System Licenses and install the new Licenses
a. Transaction SLICENSE, click “New Licenses”
b. Select Each license and go to Edit > Delete License
c. Click Install and enter the path to the license key file provided by SAP in the browse field and click Open
d. If you are unable to install the permanent license key, it may be necessary to truncate the SAPLIKEY table first, then repeat 12-c
4. Reinitialize in the transport domain
a. Logon to client 000
b. Transaction STMS
5. (Optional) Change the login screen to reflect the correct system information
a. Transaction SE61
b. Select general text, ZLOGIN_SCREEN_INFO, change
c. Change the text and save
6. Change the Logical System
a. Transaction SCC4
b. Click the edit button
c. Double-click client 100
d. Change the Client Role to Test, and save
e. Then change the Logical System to the appropriate name, and save
7. If you are using workflow, you will need to reinitialize it
a. Transaction SWU3
b. Execute the line items marked with a red ‘X’
8. If you are using BI, re-activate the system in RSA1 on the BI system
10. Verify the Adobe Document Services connection
a. Transaction SM59
b. Edit the HTTP connection ADS
c. Go to the Logon & Security tab and enter the Administrative Password in the password field, and save
d. Transaction SE38
e. Execute program FP_TEST_00, print preview to test ADS connection
f. A simple adobe form with lines and numbers will be rendered if successful
11. Apply any necessary transports
12. Change the logical spool server to point to correct system:
a. Transaction SPAD
b. Select Display for Spool Servers
c. Double click SAP_PRINT SERVER
d. Click the change button
e. In the mapping field select the appropriate application server, and save
13. Lock/Unlock users as necessary, using Transaction SU01
14. Stop and restart the SAP system
15. Run SGEN to recompile programs and reports
16. Run BDLS to change logical system
For further information you can refer SAP note
For more information about the system copy procedure, see also SAP Notes 193816 and 151603
Regards
Anand
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sel,
The System Copy Guide, which Luis linked (use the first link, the one to systems based on NetWeaver 7.0x) has an entire chapter on "follow-up activities" (it is chapter 6 in the guide). It is practically a step-by-step checklist.
With regard to some of your questions, it depends on some of the choices you made for your copy. Was this a system move, in which the SID stayed the same? Or a true copy, where you created a new SID?
1. Profiles. No, you do not copy the profiles from your source system. They have too many parameters in them that are system-specific, and will probably break your new target system. Instead, you will go into RZ10 on the new system and choose Utilities -> Import Profiles -> Of Active Servers. This will import the new profiles that SWPM created for you automatically with default settings. Then go into each profile, one by one, make any required changes (you can refer to the original profiles for tuning parameters you'd like to keep), then save and activate them. After saving changed profiles, you will need to restart the system.
2. Transport routes and configuration. It depends. Probably not. Was this system the domain controller, or will be the new domain controller? Is it remaining in the same transport domain, or going off on its own somehow? Most likely you will not change anything about your transport routes, but you will need to "add" this system into the existing transport domain, then from the domain controller "accept" (or "approve") it. If it is replacing a system in a transport route, then yes, you'll need to rebuild the routes. If it's going to be a "single system" on the side, like a sandbox or extra test system, or if this copy overwrote an existing system in the route but kept its SID (of the overwritten system), then no, you won't rebuild the routes, you'll just update the configuration. This is all done partly in STMS on the new copied system, and partly in STMS on the transport domain controller.
3. Database-level tasks. I think Luis covered this already. SWPM will have automatically setup the basic housekeeping jobs for an SAP database, except for backups. You may need to setup your backup jobs.
4. Background jobs. Again, it depends. Did you deschedule all the jobs in the source system before you copied it? If not, you'll find that a bunch of them started trying to run as soon as you started the target system, unless you manually set rdisp/wp_no_btc to 0. Whether or not they succeeded will depend on whether they tried to print before the print devices were adjusted, or needed an RFC connection that needed adjustment, etc. So, you'll need to go into SM37 and look at the "scheduled" jobs and then, one by one, determine whether or not to release them. Many production jobs are probably inappropriate for a test system, but you'll certainly want all the housekeeping jobs. If you aren't sure, you can leave them all alone and then just run a couple processes to set up new default housekeeping jobs:
a. SM36 -> Standard Jobs -> Default Scheduling
b. RZ70 -> Activate Current Configuration -> Start Data Collection and Job Scheduling
c. SA38 -> RDDNEWPP (from client 000)
You are going to have to relicense the system (in SLICENSE), adjust the spool server for all print devices (in SPAD), possibly adjust batch server groups (in SM61), possibly adjust logon groups (in SMLG), recreate or recertify SSL certificates (in STRUST), etc. Also, you may need to adjust RFC connections in SM59 in this system and in other systems that talk to it.
All of this is covered in the guide at a high level, but experience helps a lot too.
Cheers,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sel
On target system you have to use the kernel 7.21 Ext and above. kindly refer the SAP Note 1732161 - SAP Systems on Windows Server 2012 (R2)
Regards
SS
Hi Sel,
Regarding question 3.
You have to ensure that your jobs are activated in the DBACockpit, usually the installation does it already. The other post-activities regarding the database, SWPM does it already.
Another point is to ensure that you're backing up your database on regular basis (full backup > transaction log backup > differential backup > transaction log backup).
You can get more details about Backup and Restore strategy for SQL Server in note 1297986.
The other questions:
1 is more related with Software Logistics (Installation guides/Post-steps installation):
2 is more related with CTS, not sure what is the space that you could get more help regarding specific question.
And I didn't get the 4th question. Are you asking whether you could pull the background jobs from source system to run in the target system? Aren't them already there?
All the post-steps required for the system copy are documented in the installation guides, perhaps you could be more specific in which post-step you're in doubt or having issues:
In order to access the guides you must be logged into Service Marketplace.
Best Regards,
Luis Darui
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.