on 10-28-2012 7:55 AM
Dear Experts,
We are migration our SAP ECC system from one hardware to another hardware(same OS and Database).
I need to know the steps need to be taken care from the BW system regarding the BW extraction part.
Whether it will be fine once the RFC destination change alone or any other steps need to be taken care.
Regards,
Raja. G
What is the OS and DB involved?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
Since there is no changes to ECC release or patch level no need to do any thing, however from safer side you proceed as follows ( ,I did for all ECC OSDB migrations while it connceted to BW system).
Before actual migration (export / import )
1) Lock all users in ECC and BW system, except some power users who are taking care of BW jobs
2) Clenup delta 'Q' : Check RSA7 in BW system and entries must be 0 (zero). If any entry exist ask your BW team to clear these delta 'Qs'.
3) After Delta Q cleanup, disable Q's ( SMQR and SMQS) in both side
4) Disable all RFC conncetion in both side
5) BW team must stop all process chains for the migration period.
These steps are some necessary steps to avoide accidental data transfer or connection during migration period or while performing post steps.
Regards,
Dipam
Dear Raja. G,
Please ensure to follow all the steps from the installation guide
http://service.sap.com/instguides
especially the post migration follow steps regarding RFC's etc
regards,
Paul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Raja,
If you are not planning to change logical client name, hostname/ip number, you don't need to modify any configuration on the site. If you are planning to change logical client name, you should execute BDLS transaction.
Best regards,
Orkun Gedik
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
RFC configurations needs to be changed on SM59 transaction, regarding the new hostname. Do not forget to check SM55 and hosts file entries on the system, also.
Additionally, spool server on SPAD and scheduled job on SM37 configurations must be revised.
If the system is accessed over SAP portal or some other interface, certificates needs to be revised, also.
Plus, if the system is accessed by the other SAP servers and 3rd party applications, their TCP configurations needs to be revised, too.
It is good to be check the BI system with a BI consultant to be at the safe side, too.
Best regards,
Orkun Gedik
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.