BRIDGE CRM ECC V2 Consistent System Refresh

June 10, 2018 | Author: Phanikumar Thammisetti | Category: Oracle Database, Backup, Customer Relationship Management, Databases, Computer File
Share
Report this link


Comments



Description

BRIDGE TECHNICAL PROCEDURECRM and ECC Consistent System Refresh CRM 4.0 Document Information Project Name: GCS team: Document Id: BRIDGE SAP & DB Technical Delivery BRIDGE_CRM_V2_Consistent System Refresh.doc Status of the document Status Final Document. X Distribution List To Action* Due Date Comment Cc Action* Due Date Comment Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify) BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 1/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Version History Version V0.1a V0.2a V.0.2c V.1.0a V.1.0b V.1.0c Date 18.12.2006 29.10.2007 29.11.2007 23/04/2008 05/05/2008 23/10/2008 Revised By Description Markus Kleinhans François Blanchard François Blanchard François Blanchard François Blanchard François Blanchard Adding new database copy / rename procedure to take into account V2 cluster technology and file restore with BCV technology. Adding Content server repository / Spool server / ISA Catalog / TREX gateway / IPC Check / Thrusted RFC destination. Adding informations about E-Selling catalog publication target. Adding the customizing synchronization details and linking the Mustapha Outtaleb and Alexandre Komjati fisrt refresh document. Adding datafile copy / database renaming operations, export / import of RFC destination tables. Adding IPC configuration files (YY files). CRM 4.0 Validation Quality Review Method: Prepared By: Reviewed By: Review by xxx entities involved François Blanchard Date: Date: Date: Date: Validated level 1 by : Validated level 2 by : Date: Date: Date: Date: 05.11.2007 BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 2/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 Table of contents 1. Object .............................................................................................................................................................7 1.1. 1.2. 1.3. 1.4. Scope ..................................................................................................................................................7 Inputs and referenced documents ......................................................................................................8 Naming Convention.............................................................................................................................9 Different Cases for the system refresh. ..............................................................................................9 1.4.1. Case of a Project system Refresh. .........................................................................................9 1.4.2. Case of an Online Backup for the source system. .................................................................9 1.4.3. Case of an Offline backup for the Source system. .................................................................9 1.4.4. Case of a Pre-Production system Refresh. ..........................................................................10 1.4.5. London and Toltec SRDF link Schema. ...............................................................................11 2. Before the Copy...........................................................................................................................................11 2.1. 2.2. 2.3. 2.4. User information................................................................................................................................11 Backup Schedule. .............................................................................................................................11 Adding a SAP message system........................................................................................................11 SAP Preparation tasks. .....................................................................................................................12 2.4.1. Refresh Data Export Location:..............................................................................................12 2.4.2. On the SOURCE System......................................................................................................13 2.4.3. On the TARGET System (before the refresh). .....................................................................14 2.4.4. On Target system: Oracle Export. ........................................................................................15 2.4.5. Identifying online archive log generated during the backup and check for duplicate files. ..16 2.4.6. On Target System: Export RFC destination using R3Trans.................................................18 2.4.7. Target: Export RFC Thrusted destination informations. .......................................................19 2.4.8. Target: Exporting Login Screen Info .....................................................................................20 2.4.9. Target: Exporting the users before the refresh.....................................................................20 2.4.10. Exporting printers definition using SPAD..............................................................................21 2.4.11. Exporting Spool servers information (SPAD). ......................................................................22 2.4.12. Content Server: Export Repository informations. .................................................................23 2.4.13. Export IPC Configuration. .....................................................................................................25 2.4.14. Exporting TREX configuration. .............................................................................................27 2.4.15. Export SAF Tool Configuration. ............................................................................................28 2.4.16. Export E-Selling catalog information. ...................................................................................28 2.4.17. Disconnecting the Target system from CUA. .......................................................................29 2.4.18. Exporting the database structure from Source Database. ...................................................30 2.4.19. Copying the Database structure file to the target Server. ....................................................30 2.4.20. Generating Control Files for target database on the target system......................................31 Temp.sql exemple.............................................................................................................................32 2.4.21. Stopping CRM - Application on the target Host....................................................................32 BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 3/ 125 ..........1.....................................................5......... 3........................... Ensure Backup Consistency [ECC and CRM] .................. TMS Re-configuration...43 (only in case of online backup used go to the next chapter in case of offline backup).............5......................................44 3.5.................................................... Case of a project Environment refresh (Brbackup / Brrestore) (this section should be changed for V2 project systems using networker (V2) in place of Tina (V1))......................5...........................47 4.....4.....35 3............1......................... Instance Recovery: Only for PROD and PREPROD systems........2...52 Transport System Re-configuration (TMS) [CRM – ECC].44 3....................................... ....38 3...... Rename the Database............................................. ......................................................................................................... Deleting Database files on the target system......39 3........................................................................................1......... 4.....3.... 5..... ...........3..........35 3...............................33 Prepare the database restoration................45 4...........................3.............5.5...............0 2................................................................4. Case of a pre-production or production environment.......... Post copy....................... 5.....41 3. ................3...... Applying archive logs .................. ...................41 3......................................... ... Recreate the OPS$ Users...............35 3........................................................ .......2...................32 2....... .................1.......3............47 Create the new target spfile................ INT) (brbackup / brrestore).................1......3........................... Re-import SAP instance profiles [CRM – ECC]......4..............................................................2.................22..............39 3.....6..........2...4................................................................. Re-Install SAP License [CRM – ECC]......................53 5..2.......33 3.............. Post Copy: SAP tasks [CRM – ECC].2....................................... ....................................................4.........4.................... ................................ 5.................................. Checking file system size on the Target Host. ...54 BRIDGE_CRM_ECC_V2_Consistent System Refresh..51 Stopping Oracle database.................... Renaming Files systems / change owner and permission....2. Checking-Deleting old Controlfiles and old Archive logs files on target system..... Checking validity of the restored files on the target system ............4.................................................3........... Rename restored archive log to target system name...................... Case of Production and / or Pre-production environement (Clone Technology)..........................................1................................... ....4...33 3.....................38 3............................... Opening Database.................................................................................................... 4............................2.............................2.............................................. .......................................4. ....................................49 5..................................................BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4..6.51 5....................................................................................................5................................................................................ .........................4.........................................43 3.... ...............44 3...........................................................................1. Importing Oracle stuff exported before ..................34 3.... ...................4......... ... ....................4..........37 3................2.23.... RADDBDIF program........................................4.................... Starting the listener...............7........... Renaming target Database.......... ....41 3..........................53 5.........................51 Re-Starting SAP (and Oracle) instance [CRM – ECC].................. Performing the database copy..... 4...........5........39 3.............. .......... Relink database................................................................5.. Oracle tasks...........1... Restoring Database files on target host...............doc Page 4/ 125 .........................................................................53 5......................39 3................ ............................................................48 Re-importing RFC destinations table content.........................4...................4...34 3.......................... Regenerating Target control files...... Deleting the unusable entries in SAP tables :....5........47 Turning OFF the archive log mode........ Recreate /oracle symbolic link.......... Case of a Project environment (DEV.............5.......................41 3........................... .... .... ........................12............................59 Deleting unuseables SAP licenses [CRM – ECC]......................63 Restoring logon group and RFC server group [CRM – ECC] ......57 Checking the TEMSE Consistency [CRM – ECC] ..........83 6.........................87 6..........12........BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.......................55 Operation Mode configuration [CRM – ECC]............... 5........................................ 5. every client] ..........................10......11..............4. 6.......................................................................................................................65 Checking / Changing IGS RFC destination [ECC only]....... Check old RFC destinations [ECC and CRM].....79 Check Middleware Jobs [CRM.......................... ..........68 6.11... 6..................4...........................2..................................................................67 Checking RFC Destination [CRM – ECC]......... 5........................... 6................... .................56 Locking project users [CRM – ECC]...........69 Logical System Conversion (BDLS) [ECC and CRM.....................62 Check the physical Path definition............................ Middleware reconfiguration [CRM – ECC]....12........................................................................ Deleting the old profile on the target system............................. 6........5. 5.............................6........60 Re-import Printer Definition using SPAD.................. User Interface settings for IPC configuration....................... 6...........................................77 Register qRFC-Queues and Test Initial Downloads [CRM....................................................20............. 5.....16................... Maintenance of system data..55 Re-importing exported users [CRM – ECC].......1...3..................14.... 6.... every client] ......................................8....... [CRM – ECC]...............2...................................................68 6...5........................................................................21.............. Distribution Model Maintenance (ECC5) .. ...................................12.................................................................................................................75 Updating IPC customizing configuration files... 6........................................9.................................... Define URLs.............................18................................................................. 6......................72 Apply Middleware Settings [ECC..................................................... ...............13............................................... Data Exchange Conditions (ECC5) .....68 Process Entries of qRFC queues [ECC and CRM.....55 Check / Recreate Thrusted RFC destinations [CRM – ECC]...1............... 5........................................17...........1............... .............................84 6.....62 Changing SAP Directories...84 6..............................................................doc Page 5/ 125 ..................73 Apply Middleware Settings [CRM............64 Checking the system settings [CRM – ECC] ....... 5............................. 5.. ........8................12....64 Checking SAPNET Connection using SNOTE [CRM – ECC]............. Set RFC Destinations and URLs ........ ..................... every client] ........ 5.............. Importing right profiles ....12........ 5.......6.................... ..................3.......................................... 6..5................. every client]..... 6.7........23.................12....12............................................................7....................................... 5.......................................................... Re-importing logical system definition [CRM – ECC]........................................................ 5............................................55 5...... every client] ................. 5......71 Edi port and partner profile [ECC – CRM]................................................ 6........................................60 Re-import Spool servers Definition using SPAD..............................82 Manual Post Processing .. every client]...................................88 BRIDGE_CRM_ECC_V2_Consistent System Refresh..... every client] ......................... 5......68 Check RFC destinations in the target systems [ECC and CRM.........................................................19........15........................83 6.... ................................54 5.............10............5..........................2......... 5.................................0 5........ [CRM – ECC]............ ...........................................22........................................... 5...................74 Setup IPC Connection for the CRM target system [for every client]...................................................................6....................66 Restoring SLD data connection...................9................................................. 5.83 6......................64 Checking SAP Help............... ......92 Check/Correct table SMOFPARSFA ......................6............................................................... ...... 8.............10.......................................................... 8......................................................113 Database check....................................................................... 8......2......14..............98 7.......................... Change the port used for incoming sockets connections.................... 8..........5......... 8...........7.......................................9....................... Re-import Content Sever Repository informations..............6...................110 Check the configuration of the Broadcast Messaging Server.. 6................................88 6......121 Searching for critical warning or error....5.......8.. .......................................2...BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.......106 Checking / Changing CRM-SAF Tool configuration.........1.................. ........................................ Adapdation of RFC destination for ECC5 calls from CIC ..... 8............ Configure the BMS on the CRM ABAP ..................................................117 Checking the system settings and client attributes.................12..121 Re-schedule SAP Background Jobs.........119 Checking / enabeling archivelog mode... Activation of cross system lock on ECC5 ............ ............4..... ...........89 6........... 7...................120 Re-importing Delta of Transport request......... 6........................................12.....13................7........................................120 Unlocking Project Users................................................................................................ CRM components reconnexion..............................6..............................12........................ ................................................................ 8..............12.............................90 6...... ...........112 7....................................................121 Check and / or delete remaining SM02 messages....................14.............................................................................................................. Final tasks......................12...........................................................12...... 8........................12................................................................11.............0 6........................... 7........1................ 8............. 8............................118 Re-activate Oracle archive log mode............................96 Maintain Logical System for Action Box Transactions .2..........121 Re-import certificates for SSO between Portal / ESS and Portal CRM (j2ee).............................112 8.............. .........................................................3.. 6. 8.....97 Cleaning incorrect B-Doc.................13................ ........ 6.......15.............................. 7.....4............. 8.......................121 Restoring Login screen info....12..............1............122 Final Check.................116 Tablespaces free space check..99 7...................99 Re-create IPC configuration.. ........................................ .........97 Program to update table CND_MAPM_CNV_REC ..9...................................109 Make the E-Selling Catalog initial Replication.................................................... .......... Activation of cross system lock on CRM .........12.....125 BRIDGE_CRM_ECC_V2_Consistent System Refresh... 7.....................................8..................11.......................................................... ...............121 Search for critical dump........................................... 8.....................doc Page 6/ 125 ..... Connecting Systems to Central User Administration [for every client] .....................3................................................................................................10.......................................102 Checking / Changing TREX configuration......... ....................... 8.................................................112 7..................113 8. ...............................................................................12. Assign RFC destination for synchronous Method calls ..............................................................................................................6............ 7....... The synchronization is handled by the CRM Middleware. a part of the CRM server that sends business documents (BDocs) to the ECC system and processes BDocs received from the ECC system. system copy operations always have to be synchronized between ECC and CRM to ensure consistent data in the newly created or systems. the new systems will directly start to send data to the system connected to the source they were copied from (and not to each other). Because of this tight integration. because as well master data as transaction data are being synchronized all the time. All other SAP systems Scope IN OUT BRIDGE_CRM_ECC_V2_Consistent System Refresh. the connections have to be broken before the copy CRM SYSTEM Copied System ECC SYSTEM Copied System CRM SYSTEM Source System ECC SYSTEM Source System CRM SYSTEM Source System ECC SYSTEM Source System Before the client copies: The systems are connected to each other. Object The SAP Customer Relation Management (CRM) system is linked very closely to the SAP Enterprise Core Component system (ECC. Scope The list hereafter states which systems these procedure is related to: Input / Document All CRM / ECC Bridge environments with oracle database (ABAP or J2EE). Because the connection data for CRM middleware is also copied during system copy.0 1. the transmission of those BDocs is done by queued RFC calls in both directions.1.doc Page 7/ 125 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. 1. Because this would lead to data inconsistency in the target client. formerly known as R/3). To ensure that BDocs are processed in the same order as they were sent. After the client copies: Because connection data is usually also copied during the client copy. both target clients are connected to the wrong clients. 0 BRIDGE_CRM_ECC_V2_Consistent System Refresh. Inputs and referenced documents The lists of the inputs and documents are given here after: Input / Document Technical Operations Manual for SAP Net Weaver SAP CRM Powered by SAP Net Weaver Type Online documentation (click help.sap.sap.com) Online documentation (click help.com) Date Origin CRM 4.doc Page 8/ 125 .2.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 1. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 9/ 125 . Naming Convention. <SRC-SID> or <SOURCE>: Mean the source system from which the refresh is coming (source of the database backup used). so after copying. which is SAPCRM for CRM and SAPECC for ECC. 1. In most cases the refresh will be done on pre-production system refreshed by production. the database can be directly renamed and opened. <COMP NAM>: variable will be used for oracle databse shema name. CI and DB are on two different host. after restoring the datafiles you will to apply all archivelogs files generated during the backup to have a consistent system. oracle database is backuped by brtools (brbackup) so you will have to use brtools (brrestore) to restore it. no archivelog are needed because application was stopped before the backup. For all project environments.0 1. Its very important in this operation that follow use very carefully actions to perform on the Source or Target System.2.3. 1. 1. Different Cases for the system refresh.4.4.4.3. but sometimes you will have to do it on some project environments. CLUSTER environement: You can find some remarks for system with HACMP functionality (PROD. BRIDGE_CRM_ECC_V2_Consistent System Refresh. an ECC to an ECC etc…)). Different cases are possible to perform a system refresh (Refresh means: Making a database copy from an existing system to another existing system of the same solution (you can only copy a CRM to a CRM.1. NON-CLUSTER: All other project environement (DB / CI are on the same server). Case of an Offline backup for the Source system. Case of an Online Backup for the source system. For an offline backup. In case of online source backup. PREPROD & MAINT). <TAR-SID> or <TARGET>: Mean the target system for the database restore (target mean the system to be refreshed).4. 1. Case of a Project system Refresh. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. • • • • • • • • • • • • • • • • • • • • • • • • SAP: Refresh preparation: Export all needed data on TARGET system before the refresh (export DBS / listener config / users profiles. The Production disk Array in London is continuously synchronized with the Pre-Production DR (disaster Recovery) disk array in Toltek by a SRDF link. reopening target database and doing all post-refresh steps. SAP: export RFC destination table. SAP: Stop SAP and oracle on Target system.4. Case of a Pre-Production system Refresh.doc Page 10/ 125 . For pre-production and production system. SAP: Make all post refresh tasks (Middleware resynchronization). permission and oracle symbolic links) the SAP team task starts with restarting database (Instance recovery without database rename.).0 1. UNIX: Backup Scheduling on source system (BCV Splitt).. listener config on target system SAP: recreate /<server/oracle link. SAP: Generate Trace file on source system to prepare target controlfiles. modify oraarch owner SAP: Relink all (oracle) SAP: Regenerate target control files (Database rename). applying archive. SAP: Import DBS. SAP: Apply Archive logs (only in case of online backup). UNIX: Rename file systems. SAP: Instance recovery (startup DB on target without renaming). modify oracle files (clntsh. the backup is performed by a SRDF link between the two site of London (PROD) and Toltek (Pre-Prod). SAP: Open database (resetlogs).4. Tools: Deschule Backup jobs on target system (and all jobs). SAP: Unlock users SAP: Schedule backup an jobs on target system BRIDGE_CRM_ECC_V2_Consistent System Refresh. SAP: Lock SAP users on target system. UNIX: Copy ORAVG and REDOVG from source to target system (change /<preprod servr>/oracle link to prod server name). user profiles. SAP: Change /oracle owner to prod sid. SAP: Restart SAP. SAP: Recreate oracle users. For a refresh. renaming the database. So. Refreh steps list for preproduction system-refresh. The Unix team take the charge of copying databases files between the two servers and renaming files system (owner. change oraarch owner (oraarch is not part of ORAVG). start backup and check return code. SAP: Shutdown DB on target system. change oracle library links. SAP: Change RFC destination (to avoid send data on prod systems). no brtools are used in this case (prod / preprod). delete RFC hostname informations. the source database is switched in Begin-backup state and the DR disks are synchronized with the pre-productions ones. 4. 2. be sure that the backup is well scheduled. London and Toltec SRDF link Schema. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Adding a SAP message system. 2. Before the Copy. be sure to use the same backup time stamp for ECC and CRM systems. On the Source system. 2. 2. You can use SM02 to create a system message with the following kind format. User information.3.2.doc Page 11/ 125 . Make sure that all users have been informed of the next system refresh.0 1. Backup Schedule.5.1.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. doc Page 12/ 125 .. you can (have to. to save the data in flat file that you can record on your PC and reuse to recreate the data manually.1.0 2. oracle table export / import (if corresponding scripts have been created or other tools). UNIX export location: Path: zdbackup:/sapcd/REFRESH/EXPORT Windows Export Location: N:\GTCC\Technical_Design_and_Build\02-SAP & DB Build\05.4. you will have to extract (or save) data in the target system before deleting it (to be able to recreate them after the system copy). during and after the refresh. To do it you can use some screen copy. 2.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. you can use the “system List Save” Menu path. For each transaction data to be exported. Refresh Data Export Location: Two directory were created to temporary store exported before. SAP Preparation tasks.) use them for your refresh.Administration Procedures\11 REFRESH\EXPORT To be able to recreate connections with other systems and for other purpose. use the following path: BRIDGE_CRM_ECC_V2_Consistent System Refresh.4. Target Oracle and SAP users must be authorized to access the Tina Source catalog. SAP ECC / CRM Source BRIDGE_CRM_ECC_V2_Consistent System Refresh. SOURCE or TARGET ECC / CRM Source Remarks OK / KO TEAM SAP SAP ECC / CRM Source Logon with ora<sid> on the target system and use the following command: Ora<sid>/ sqlplus ‘/ as sysdba’. SAP ECC / CRM Source SQL> alter database backup controlfile to trace.trc will generated in: /oracle/<SID>/saptrace/usertrace When backup is completed Use DB12 to check the backup return code. you cannot restart database before it is in a consistent state. Connected. DB12: Identify archive log to be applied in case of Online backup. Task or Transaction code Before the backup.4. !!!Just before the backup: Export the source database structure. check with SM13 if you don’t have any interrupted update. A new file with form <sid>_ora_xxxx.2.4.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. ask functional team to cancel or validate if yes. to do that you need to identify which archive have been generated during the backup and restore them into the target oraarch directoy (this step is described in point 2. If you have to restore an online backup. The Unix – Backup team is the owner of this tasks (no possible restauration without it). Check the backup is cheduled at the Same time within ECC System.3). On the SOURCE System. SAP UNIX – Backup Team ECC / CRM Source ECC / CRM Source Check that no new datafiles were added during the backup (if yes you will have to recreate a new control file).doc Page 13/ 125 .0 2. SOURCE or TARGET ECC / CRM Target. Export on a flat file (system list Save) or make a screen-shot of AL11 transaction. Must be done just before the database restore Ask the right team to do it (Tools Team). Make screen-shot for all non-standard RFC destination with all connexion details (user.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 2. ECC / CRM Target. Make a screen shot and be sure to have each port-number and associated RFC BD54: Export All logical system. ECC / CRM Target.3.*” to export all user profiles Deschedule backup planned during the system refresh SAP ECC / CRM Target. client. Use brtools to make an export of table RFCDES and RFCDOC.Unix Oracle EXPORT (DBS) Export the followings on zdbackup/sapcd/REFRESH/EXPORT /oracle/<SID>/102_64/dbs /oracle/<SID>/102_64/network/admin /oracle/<SID>/oraInventory SAP ECC / CRM Target. ECC / CRM Target. (If jobs are not scheduled in ControlM you will have to use SM37 to take all scheduled / released jobs details to be able to reschedule them after the system copy). SMT1: Export RFC thrusted destination informations. On target database nodes. Export on a flat file (system list Save) or make a screen-shot of WE20 transaction.4. SAP SAP SAP SAP ECC / CRM Target. Make screenshot of RZ03 and RZ04. Spad Output devices Edit Transport All Create a transport. IPC: Export IPC configuration (table. CONTROLM ECC / CRM Target. (be carefull with outbound / intbound parameters). ECC / CRM Target.…). Must be done just before the database restore Ask the right team to do it. you will have to backup a Export Oracle User profiles. ECC / CRM Target. SAP ECC / CRM Target. Screen copy Screen Copy. use “cp .0 Task or Transaction code !! Check you have sufficient space in the target system /oracle/<TARSID>/sapdataxx for the source database. On the TARGET System (before the refresh). Create a transport request with all logical system. ECC / CRM Target. CRM 4. Logon with ora<sid>. RZ03 / RZ04: Make screenshot of operation mode definition AL11: Export all SAP Directories definition. SAP BRIDGE_CRM_ECC_V2_Consistent System Refresh. release it and note the transport request number. SAP SAP SAP SM59: Export all RFC Destination (table RFCDES and RFCDOC SAP ECC / CRM Target. SPAD: Export the Spool server definition. release it and note the transport request number. WE20: Take a screen shot of the Partner type LS and US. TEAM Remarks OK / KO SAP . Deschedule Jobs in the target system. WE21: Take a screen shot of ALL ALE Port number.doc Page 14/ 125 . ECC / CRM Target. Make screen shot of thrusted system (ECC / CRM° . export certificate information. SAP ECC / CRM Target. CSADMIN: Export repository information. Copy all file of user profile of ora<sid> Tools ECC / CRM Target. SPAD: Export the printer definition. COMM_IPC_DEST / COMM_IPC_URL) Screen shot TREX: Export TREX configuration (trans: SRMO) Content Sever: (OAC0 / STRUSTSS02. Because ORAVG volume will be copied from source during the refresh. doc Page 15/ 125 . launch SCUA. ECC / CRM Target.4. with SAP_USER profile) for each client on the target system. to be abble to restore the system in the same state. You can use saplicense transaction or. SAP SAP SAP SAP ECC / CRM Target ECC / CRM Target. ECC / CRM Target. if yes take a screenshot to be able to restore it (see detail in step: 2. SLDAPICUST: make screen shot SLD hostname RZ04: Export operation mode configuration (screen shot). Make a screen shot (work process and time distribution). SE61. zlogin_screen_info Exporting the SAP welcome message SM69: Export all Specific External command defined. ECC / CRM Target. Make a client export (client copy. cd $HOME. you can launch saplicense – show command. SCC4: Client attributes SLICENSE: Extract the SAP License data. note the request numbers and release them when the export was finished. Lock all PROJECT USERS. export profiles of ora<sid> and <sid>adm (for ora<sid> user. SAP ECC / CRM Target. ECC / CRM Target. Use SM63 to display and save the time table. as <sid>adm.4. 2. SAP SAP ECC / CRM Target. ECC / CRM Target. chek by using SU01. Take a screen shot of each client attributes. cp –p .* /sapcd/REFRESH/EXPORT/CRM/QCA/profiles/ora<sid> (do the same for <sid>adm). On Target system: Oracle Export. Because you will have to lock all user before restarting SAP. make a client export for all client to be refreshed. Export Oracle Stuff: Copy the content of the followings directory on /sapcd/REFRESH/EXPORT/”component” • • • • /oracle/<SID>/102_64/dbs /oracle/<SID>/102_64/oraInventory /oracle/<SID>/102_64/network/admin On DB Node. SMLG: Take a screen shot to be able to recreate all Logon Groups RZ12: Take a screen shot to be able to recreate all RFC Server Groups RZ70: Take a screen shot to be able to recreate the SLD system connexion. the create button must be there. check child system = the refreshed system and use the trash to delete it. ECC / CRM Target.4. CRM 4. Check if there is a message. ECC / CRM Target. On the target system. BRIDGE_CRM_ECC_V2_Consistent System Refresh. SAP ECC / CRM Target. Make a screen shot. ECC / CRM Target. Make a screen shot and be sure to have all groups details.8 Extract the data containing an hostname or SU10 SAP SCC8: User Eport.0 SAP SAP SAP SUIM: Display and save in a local the locked user list. SAP SCUA: Disconnect the client from the CUA central system.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh destination in the screenshot. take a list of the locked user before the refresh. Launch DB12 and choose “overview of database backups”.doc Page 16/ 125 .5. Identifying online archive log generated during the backup and check for duplicate files. you will have to apply all archive log generated during the backup To identify archive log generated during the backup do the followings: Logon to the source system. Identify the backup that you want to use to restore (and open the detailed log). For the target database to be consistent.0 2. In this screen. BRIDGE_CRM_ECC_V2_Consistent System Refresh. check that you have no duplicate data files (2 files with same name even if they are in different locations).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.4. *Only in case of online backup used for the system copy. Here you have only the log sequence number.0 Click on the “detail log” button. At the beginning of the log you can check the archive log sequence used during the backup. BRIDGE_CRM_ECC_V2_Consistent System Refresh.dbf By returning to the first DB12 screen you can use the following to know the real archive log file and if you have to restore to a defined time stamp you can check wich archive files you will have to restore to do it. the complete archive is composed by the followings: <SID>arch1_<log sequence number>_<number>.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 17/ 125 . Objective of this step is to export all RFC destination (by exporting content of all RFC tables) of source system to be able to restore them after the refresh (and before restarting the target system).ctl EXPORT CLIENT=000 (*rfc tables are client independent tables). Logon to the target system with user <sid>adm Go to /oracle/<TAR SID>/sapreorg Create the parameter file using “vi” command (file name: export_rfc. Note: All exported data will be temporary stored into /oracle/<SID>/sapreorg Procedure: Creates R3trans parameter file containing the table list to be exported.zr0adm Time Navigator environment has been correctly set zr2serv:zr0adm 1> cd /oracle/ZR0/sapreorg zr2serv:zr0adm 2> vi export_rfc.doc Page 18/ 125 .0 In this screen you can check which archive log file you will have to restore in target oraarch directory to recover database to the needed time stamp (*should be same time stamp for ECC and CRM systems). On Target System: Export RFC destination using R3Trans. zr2serv:/oracle/ZR0/sapreorg>cd zr2serv:/>su .dat’ SELECT * from RFCDES SELECT * from RFCDOC SELECT * from RFCATTRIB SELECT * from RFCCHECK SELECT * from RFCDESSECU SELECT * from RFCSYSACL SELECT * from RFCTRUST SELECT * from RFCCMC SELECT * from RFCGO SELECT * from SXRFC SELECT * from IBSSI_RFCDEST BRIDGE_CRM_ECC_V2_Consistent System Refresh.4. FILE=’sm59_<SID>.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. 2.6.ctl). to avoid refreshed target system try to communicate with some client of the source system). 25. Target: Export RFC Thrusted destination informations.doc Page 19/ 125 . Check the R3trans return code ! This command create the file sm59_<SID>. 2.ctl zr2serv:zr0adm 7> R3trans -w export_sm59.log (name added in the export command line).07.log export_rfc.4.ctl This is R3trans version 6.06 . Launch transaction smt1 BRIDGE_CRM_ECC_V2_Consistent System Refresh. unicode enabled version R3trans finished (0000). zr2serv:zr0adm 9> pwd /oracle/ZR0/sapreorg zr2serv:zr0adm 10> ls –ltr The table export is now ready to be imported latter (RFC data must be updated just after database rename and before starting the target SAP system!). and the log file export_sm59.13 (release 640 .log export_rfc.dat (created before) which contain exported table content. Use command: R3trans –w <export log file name> <parameter file name> Exemple for ZR0: R3trans –w export_sm59.7.0 Execute the R3trans export.17:34:00). Logon to target system.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Exemple on ZR0: CRM 4. Choose data element ZLOGIN_SCREEN_INFO Choose change. To be able to logon with the same password to the refreshed system after the system refresh. Release the transport request and not the transport request number. Target: Exporting Login Screen Info Launch se61.4. Create a transport request with your change (no change here. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Target: Exporting the users before the refresh.8.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. all user need to be exported for all needed client).doc Page 20/ 125 . change mode is only to create a transport request.4. 2.0 2.9. Choose Menu Edit Transfer Export and make the following selection* BRIDGE_CRM_ECC_V2_Consistent System Refresh.4. He will be usefull for the client Import. 2. Exporting printers definition using SPAD. Release the Transport Request (User transport request name would be: <target SID>KTxxxxxx). Note: Make sure that there is enough space in the directory /usr/sap/trans Use SCC3 Tcode to survey the export.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Switch in change mode. Note the transport Order. Launch SCC8 transaction. Select the profile SAP_USER Be sure that target system = <TAR-SID> Note the transport request number.10.doc Page 21/ 125 . Launch transaction SPAD Use the “printer button”.0 Log on the Target system in the client the users have to be kept. Exporting Spool servers information (SPAD).doc Page 22/ 125 .11. use the “export” functionality for OMS. BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. 2.0 Check the export log Check the file on your PC.4. First. Use the “Spool servers” Button. Content Server: Export Repository informations.12. servers during post refresh activities. Double click each servers and make a screen copy to able to reconfigure / check both. CRM 4. Launch transaction OAC0. double click the line Z_<CS SID>_TEST BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 Make a screen copy. 2.doc Page 23/ 125 .4.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Use transaction SPAD. CRM 4.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Use the “full administration” button and make a screen copy. Make a screen copy of tab “certificates” and “Settings”.doc Page 24/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 Click the “CSADMIN” button (or launch transaction “CSADMIN”. doc Page 25/ 125 .13. Export IPC Configuration. those export must be done in every needed clients.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 Launch transaction “strustssO2” and make a screen copy. Make the following screenshot to export connected IPC information: In case of several client.4. Check and export IPC Release informations: Launch transaction: TTE_SIMULATION Launch transaction SE16: Fill-in table name: COMM_IPC_DEST BRIDGE_CRM_ECC_V2_Consistent System Refresh. 2. BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Fill-in table name: COMM_IPC_URL CRM 4.0 Export RFC Destination Information Launch SM59: Double click Dispatcher and Server destination and take screen shots.doc Page 26/ 125 . Exporting TREX configuration. Tab: Search Server Relation Tab: RFC Destination Launch SM59 to take screen shot of TREX RFC Destinations: BRIDGE_CRM_ECC_V2_Consistent System Refresh.4.doc Page 27/ 125 .0 2. Launch transaction SRMO: Take screenshots of both tabs “Search Server Relation” and “RFC Destinations”.14.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Launch transaction se16 and export (screen copy or “save list as.15.doc Page 28/ 125 .”) for the following table.16. CRMC_SAF_APP_RFC 2. Launch transaction SPRO: BRIDGE_CRM_ECC_V2_Consistent System Refresh..BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.4. Export SAF Tool Configuration.4.0 2. Connect target system. Export E-Selling catalog information. doc Page 29/ 125 .0 Double click each server and take screenshot of all detailed informations.17. Disconnecting the Target system from CUA. 2.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.4. Launch transaction SCUA. Logon to the target System. BRIDGE_CRM_ECC_V2_Consistent System Refresh. 2.4. Database altered A new trace file with form: <sid>_ora_xxxx. This operation must be done just before launching the backup (to be sure that no modification were done on the database).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. SQL> show parameter user_dump_dest NAME TYPE VALUE -----------------------------------.0 Use the trash button to delete the system (!!! be sure to do it only for the target system only).trc into the same directory on target host: /oracle/<TAR SID>/saptrace/usertrace). this file will be then used to recreate target control files and to rename target database.trc will be created in directory: /oracle/<SRCSID>/saptrace/usertrace (or at the emplacement of oracle parameter: user_dump_dest. To be able to rename the database on the target server when file will be copied. BRIDGE_CRM_ECC_V2_Consistent System Refresh.19. SQL> connected SQL> alter database backup controlfile to trace.----------. you must check after the backup in the source system alertlog that no new datafile were added during the backup. <ora>sid/ sqlplus ‘/ as sysdba’.-----------------------------user_dump_dest string /oracle/<SID>/saptrace/usertrace 2. Copying the Database structure file to the target Server. On the source system: To be able to regenerate the control files on the target system you must extract the exact database structure in a file. you have to copy the trace file generated in preceding step.4. this file then will be copied on the target server to be used to generate the corresponding control files.18.doc Page 30/ 125 . Exporting the database structure from Source Database. Logon to the source system with user ora<sid> Launch sqlplus and connect database: sqlplus ‘/ as sysdba’. Copy the trace file (<src sid>_ora_xxxx. Use command: alter database backup control file to trace. sql like the following: ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/ <TAR SID> /sapdata3/temp_2/temp.$s%<Source SID>%<Target SID>%g Cut the lines relative to TEMP FILE Creation and create a script named temp. using the following command: :1.dbf'. GROUP 24 ( '/oracle/<TARGET SID>/origlogB/log_g24m1. Add the lines relatives to Tempfile in a file temp. '/oracle/<TARGET SID>/mirrlogA/log_g23m2.dbf' ) SIZE 150M.dbf'. CHARACTER SET UTF8 . temp file is not backuped anymore). rename the trace file (<src sid>_ora_xxxx. 2. '/oracle/<TARGET SID>/mirrlogA/log_g21m2.sql (cmd: “mv <src sid>_ora_xxxx. the first lines should be: STARTUP NOMOUNT CREATE CONTROLFILE SET DATABASE "<TAR SID>" RESETLOGS NOARCHIVELOG” ….sql”). open the file /oracle/<TAR SID>/saptrace/usertrace/control.sql which will be used to regenerate the target control files. Delete the last lines of the file.dbf'.4.0 On the target system. GROUP 23 ( '/oracle/<TARGET SID>/origlogA/log_g23m1.20.dbf'.sql Suppress the line at the beginning of the file. GROUP 22 ( '/oracle/<TARGET SID>/origlogB/log_g22m1.trc control. SID> " RESETLOGS ARCHIVELOG BRIDGE_CRM_ECC_V2_Consistent System Refresh.data2' SIZE 4096M REUSE AUTOEXTEND OFF.doc Page 31/ 125 .dbf' ) SIZE 150M.sql exemple: STARTUP NOMOUNT CREATE CONTROLFILE REUSE DATABASE "<TAR MAXLOGFILES 255 MAXLOGMEMBERS 3 MAXDATAFILES 254 MAXINSTANCES 50 MAXLOGHISTORY 2629 LOGFILE GROUP 21 ( '/oracle/<TARGET SID>/origlogA/log_g21m1.. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/<TAR SID> /sapdata3/temp_1/temp.sql which will be used to recreate the Temp file (because in new release.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. On the target system. Change the SID relative to Source system to SID of the Target system. '/oracle/<TARGET SID>/mirrlogB/log_g22m2. Generating Control Files for target database on the target system.dbf' ) SIZE 150M. Copy those two files in the /sapcd/REFRESH/EXPORT/<component>/<SID> directory.data1' SIZE 629145600 REUSE AUTOEXTEND OFF. Rename the trace file with new SID to control. the last lines should be: …. Control.trc) copied in the preceding step to name: control. data3'. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/ZC0/sapdata3/temp_1/temp.data1'.data8'.data4'. you must ensure that there is sufficient freespace available on the target file systems. '/oracle/<TARGET SID>/sapdata2/crm620_6/crm620.doc Page 32/ 125 . Checking file system size on the Target Host. Clean IPC: as <sid>adm cleanipc <inst number> Stop the Oracle listener (as ora<sid> lsnrctl stop LISTENER_<SID> Check with “ps” that all processes have been stopped.doc” Ask Tools team to stop the monitoring (Tivoli and Solution manager). Gateway) have to be stopped.STANDBY LOGFILE DATAFILE '/oracle/<TARGET SID>/sapdata1/system_1/system.data2'. GROUP 26 ( '/oracle/<TARGET SID>/origlogB/log_g26m1. For the CRM. '/oracle/<TARGET SID>/sapdata2/undo_1/undo.4. Temp. BRIDGE_CRM_ECC_V2_Consistent System Refresh.sql exemple ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/ZC0/sapdata3/temp_2/temp.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh '/oracle/<TARGET SID>/mirrlogB/log_g24m2. TREX. '/oracle/<TARGET SID>/sapdata3/crm620_1/crm620. 2.data1' CHARACTER SET UTF8 CRM 4.dbf' ) SIZE 150M. '/oracle/<TARGET SID>/sapdata4/crm_3/crm. '/oracle/<TARGET SID>/sapdata1/crm_8/crm.data5'. Gateway. '/oracle/<TARGET SID>/sapdata3/crm620_3/crm620.data5'.data8'. '/oracle/<TARGET SID>/mirrlogA/log_g25m2.data7'. Stop all other application running (IPC.dbf' ) SIZE 157286912 -.data1'.data2' SIZE 4096M REUSE AUTOEXTEND OFF. '/oracle/<TARGET SID>/sapdata4/crm_2/crm. '/oracle/<TARGET SID>/sapdata1/undo_2/undo. Stopping CRM . '/oracle/<TARGET SID>/sapdata4/crm_5/crm.data1'. '/oracle/<TARGET SID>/sapdata1/crm_9/crm.data9'.0 .data6'.dbf' ) SIZE 157286912.21. '/oracle/<TARGET SID>/sapdata1/crm620_7/crm620.data2'. '/oracle/<TARGET SID>/sapdata1/crmusr_1/crmusr. '/oracle/<TARGET SID>/sapdata4/crm_6/crm. To be able to restore the source database in the target file system. 2.dbf'. all components (R3. '/oracle/<TARGET SID>/sapdata4/crm620_8/crm620.data3'.dbf'. '/oracle/<TARGET SID>/sapdata1/system_2/system. '/oracle/<TARGET SID>/sapdata1/sysaux_1/sysaux.Application on the target Host. Stop SAP on all applications servers (as <sid>adm stopsap r3) Stop SAP and Oracle on Central and database instance (as <sid>adm stopsap).data1'. '/oracle/<TARGET SID>/sapdata3/crm620_4/crm620. Now we will have to stop SAP and other application on the target server (ECC and CRM).data2'.data1' SIZE 629145600 REUSE AUTOEXTEND OFF. Content server).data6'.22. Ask the Tools team to stop the Jobs scheduler. '/oracle/<TARGET SID>/sapdata3/crm620_2/crm620. use the right procedure: “BRIDGE_CRM_V2_Starting and Stopping CRM. GROUP 25 ( '/oracle/<TARGET SID>/origlogA/log_g25m1. '/oracle/<TARGET SID>/mirrlogB/log_g26m2. IPC.data4'. '/oracle/<TARGET SID>/sapdata4/crm_4/crm. '/oracle/<TARGET SID>/sapdata1/crm_7/crm. J2EE.data7'.data1'.data2'.4. TREX. '/oracle/<TARGET SID>/sapdata4/crm_1/crm. '/oracle/<TARGET SID>/sapdata2/crm620_5/crm620. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 The target file system must have the same size that source or must have sufficient freespace to store the utilized FS size from the source. On the target host, check the following File systems size: /oracle/<SID>/sapdata<n> (1 to n) /oracle/<SID>/oraarch /oracle/<SID>/saparch /oracle/<SID>/mirrlogA /oracle/<SID>/mirrlogB /oracle/<SID>/origlogA /oracle/<SID>/origlogB 2.4.23. Deleting Database files on the target system. *Note: To be done before deleting target datafile: Be sure that the source system backup is successfull Inform project if not OK. Be sure there is no duplicate name of backuped files (even in different location, brrestore is not able to restore 2 datafiles with same name even if they are in different location), could be checked into the source backup detailed log file. Be sure that no new datafiles where added to the source database during the backup (check that there was database structure change during the backup, could be checked in the source alerlog file). Log on the target system with user ora<sid>. Suppress all the old target data files in each /oracle/<SID>/sapdata* directory using the command rm –r in the sapdatas directories (you must the sapdatas directory when launching command “rm”). Delete the content of the following directories : /oracle/<SID>/sapdata<n> (1 to 4) /oracle/<SID>/oraarch /oracle/<SID>/saparch /oracle/<SID>/mirrlogA /oracle/<SID>/mirrlogB /oracle/<SID>/origlogA /oracle/<SID>/origlogB 3. Performing the database copy 3.1. Ensure Backup Consistency [ECC and CRM] Because of data replication mechanism between ECC and CRM System, both system databases need to be recreated with the same time stamp, it means that in case of offline backup the begin backup phase must be done at the same time in ECC and CRM, and in case of online backup the begin backup as less importance, but you will have to apply archive log until exactly the same time stamp. The backup time stamp for applying archive must be known (Coordination ECC / CRM) BEFORE STARTING THE RESTORE. BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 33/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 3.2. Prepare the database restoration. 3.2.1. Case of a project Environment refresh (Brbackup / Brrestore) (this section should be changed for V2 project systems using networker (V2) in place of Tina (V1)). In case of project refresh, we will use brbackup / brrestore program and in this case we have to autorize the target system to access the source tina catalog. a. Enabling the restore from the source to the target host (Unix – Backup Team). You must ask the Unix team to authorize the target users (ora<sid> and <sid>adm) to access the source catalog (Tina Team). b. Copying the backup log file from source to target system. On the Source System. Log on the source system with user ora<sid>. Go to the directory /oracle/<SID>/sapackup. Identify the last backup log (cf DB12 under SAP to find the corresponding file name). The file would be *.aff for an offline backup and *.anf for an online backup. CRM 4.0 Copy the file to the /oracle/<TAR SID>/sapackup directory of the target host. Change the rights of the file on the target system with the target user and the group : “chown ora<target sid>:sapsys <file name>” c. Modifying the init<SID>.utl on the target host. On the Target System. Go to the directory /oracle/<SID>/102_64/dbs. Make a backup copy of the original init<SID.utl (“cp –p init<SID>.utl init<SID>.utl.backup”). Modify the file init<SID>.utl on the target system. The field “folder” should be changed to the value of the source system. init<SID>.utl catalog sch5 (could be different, catalog used could be checked in the backup log). BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 34/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh folder <source host>_<SRC SID> tmp_dir /tmp CRM 4.0 Exemple:”dc2serv_DCB” (if the source is DCB on dc2serv). d. Checking Brtools release on the target system. Log on to the target system with user ora<sid>. Check the brtools version by using brtools –V command. Make sure you use at least BRTOOLS 6.40 (patch 36) for V1 systems and BRTOOLS 7.00 (patch 24) for V2 systems. Here is screenshot for V2 systems. 3.2.2. Case of a pre-production or production environment. For pre-production and production environment, when database are deleted there is nothing else to prepare because Unix is responsible for restore the source database from the Disk Clone (you can directly go to the restoration chapter) Unix team copy the ORAVG and REDOVG from production to production servers (you only have to check that dbs, network, oraInventory and ora<sid> user profiles are exported (in addition of all SAP stuff). 3.3. Restoring Database files on target host. 3.3.1. Case of a Project environment (DEV, INT) (brbackup / brrestore). On the target system: Logon with ora<sid> user. Go to the directory /oracle/<SID>/sapackup Start the restore with the command : brrestore –b backup_file (use the backup file copied above ) BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 35/ 125 's[top]' to cancel BRRESTORE: Enter ‘c’ to continue.37. BR0406I End of file restore: rdvrhjob.56. Changing back the init<SID>.320 MB BR0421I Restore device type: util_file BR0280I BRRESTORE time stamp: 2006-09-27 08.45.14 BR0280I BRRESTORE time stamp: 2007-07-11 13.44 BR0416I 41 files found to restore. backup bdtojmok.doc Page 36/ 125 .utl to the original one (if no.. total size 88140.22 BR0256I Enter 'c[ont]' to continue. The restore will start.30.0 qg2serv:oraqgv 1> brrestore -b bdtojmok. check for the warning).22 BR0407I Restore of database: QGV BR0408I BRRESTORE action ID: rdtozxwx BR0409I BRRESTORE function ID: rsb BR0449I Restore mode: ALL BR0419I Files will be restored from backup: bdtoygbc. BR0427I Files from the old sapdata_home /oracle/PGV will be restored into the new sapdata_home /oracle/QGV BR0370I Directory /oracle/QGV/sapdata1/ecc_12 created BR0370I Directory /oracle/QGV/sapdata4/ecc_11 created BR0370I Directory /oracle/QGV/sapdata3/ecc_10 created … BR0370I Directory /oracle/QGV/sapdata1/system_2 created BR0370I Directory /oracle/QGV/sapdata1/system_1 created BR0280I BRRESTORE time stamp: 2006-09-27 08. BRIDGE_CRM_ECC_V2_Consistent System Refresh. your next backup on the target system will be done on the source folder !).aff 'PGV' BR0455W Value 'QGV' of oracle_sid will be used for restore BR0454W Values of oracle_home are different: current '/oracle/QGV/920_64'.17 BR0256I Enter 'c[ont]' to continue.aff '/oracle/PGV' BR0455W Value '/oracle/QGV' of sapdata_home will be used for restore BR0280I BRRESTORE time stamp: 2006-09-26 14.17 BR0454W Values of oracle_sid are different: current 'QGV'.45. If the sapdatas doesn’t exist. ….56. A warning message appears because SID in the file init<SID>.aff BR0401I BRRESTORE 6.37.rsb 2007-07-11 13.aff '/oracle/PGV/920_64' BR0455W Value '/oracle/QGV/920_64' of oracle_home will be used for restore BR0454W Values of sapdata_home are different: current '/oracle/QGV'.rsb 2006-09-26 14.14 BR0403I BRRESTORE completed successfully with warnings !! Now it’s very important to change back the init<SID>.sap and the backup_log are not the same (this warning is normal).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.. 's[top]' to cancel BRRESTORE: Enter ‘c’ to continue. Check the brrestore return code (must be succesfull or successful with.utl file.40 (15) BR0405I Start of file restore: rdtowhbl.aff 2006-09-27 00. backup bdtojmok. backup bdtojmok. the tool will create them: BR0259I Program execution will be continued. utl Check the followings in the init<SID>.backup init<SID>. BRIDGE_CRM_ECC_V2_Consistent System Refresh. the Unix team (infrastructure team) is responsible to restore the database data of production environment into pre-production server. folder zc2serv_ZC0 Should be the target system name and server. Case of Production and / or Pre-production environement (Clone Technology). Use command mv init<SID>.0 Logon to the target system. Here PCA ORAVG was copied on QCADB server: Here PCA REDOVG was copied on QCADB server: Ask UNIX team to restore production VG on pre-production server. Technology used is clone / BCV which consist to make a flash (quick) copy / synchronisation of the production or pre-production disks to another disk array. zc2serv:/oracle/ZC0/102_64/dbs>more initZC0.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. the ORAVG and REDOVG from production.utl.utl file (or create it like that if you have no backup). this copy is then backuped on tape (advantage of this kind of architecture is that unavailability duration of production and preproduction systems is reduced in comparaison with brbackup (disk synchronisation is a very quick process. For Production and pre-production systems. Go to /oracle/<SID>/102_64/dbs Use command rm init<SID>. tmp_dir /tmp 3. only a few minutes needed)).utl (to delete the incorrect ones). backup / restore are not performed by brbackup / brrestore tools.2.3. Here is the list of file system copied during this operation. Unix team will copy on pre-production servers the volume group ORAVG and REDOVG.utl catalog sch5 Should be the catalog defined for the target system.doc Page 37/ 125 . So in this case. Ask the UNIX team to copy on pre-production server. BRIDGE_CRM_ECC_V2_Consistent System Refresh. You must see the followings (see the screenshot above about PCA VG). For PROD and PREPROD systems.doc Page 38/ 125 . Now you will have to restart the database (SRC) on target server (without renaming !). Give them the database source <SID> / server and target <SID> / server. At the end you must see the followings on pre-production server.” RestartDB: “startup” When database is opened. Create the /<srcsid>db/oracle link (“ln –s /<srcsid>db/oracle oracle”).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Changing /oracle and /oracle/<SID>/oraarch owner to <src>sid owner. Instance Recovery: Only for PROD and PREPROD systems. • • Use the following to check if all file system have been copied: “lsvg –l <TARSID>oravg” and “lsvg –l <TARSID>redovg”.4. • • • Delete the /<tarsid>db/oracle link (“cd /” and “rm oracle”). When Unix team as completed the Volume Group copy. Changing /oracle symbolic link.4. • • • • • Connect db server as ora<tarsid> Launch sqlplus “sqlplus ‘/ as sysdba’. 3. Shutdown it with “shutdown immediate”. 3. At the end you must see the followings Restarting Oracle database (Instance recovery). At this point UNIX team must rename file systems on preprod server. be sure to restore all archive log needed (3 files before the backup stars and 3 files after the backup is finished on source system).0 In case of online backup used. and changing oracle library links (Ask Unix team to do it).1. Renaming Files systems / change owner and permission. group : dba saparch. copy back the ora<sid> and <sid>adm profiles on each home directory. Relink database. Subdirectories should have the permission code 640 and the user : ora<sid> . Importing Oracle stuff exported before (only for PREPROD / PROD). • Logon as ora<sid> • Launch command: “relink all” 3.4. directories and subdirectories should have the permission code 755 and the user : ora<sid> .4. To change permission qg2serv:oraqgv 21> cd $HOME qg2serv:oraqgv 22> chmod -R 755 sapdata* If the user and group are not well positionned : To change owner qg2serv:oraqgv 22> cd $HOME qg2serv:oraqgv 23> chown -R ora<sid>:dba sapdata* Logon to the target system with user ora<sid> and check the following (file time stamp and file location under home directory of ora<sid> user).0 Delete the /<prodsid>db/oracle link and recreate the link for preprod. • • • • On the target. group : dba.4. 3. Checking validity of the restored files on the target system Checking User. At this point you will have to relink the database.oraarch.2. • • • • • • Recreate /oracle symbolic link.4. BRIDGE_CRM_ECC_V2_Consistent System Refresh.mirrlog and origlog directories should have the permission code 755 and the user : ora<sid> . copy back the dbs directory under /oracle/<SID>/102_64 On the target. Check / Change permission of /oracle and oraarch directory to ora<tarsid> 3.3.doc Page 39/ 125 . All the sapdatas. Group.5. copy back the oraInventory directory under /oracle/<SID> On the target. Authorizations of the restored files. Use cd $HOME Use: rm oracle Use: “ln –s /<tarsid>db/oracle oracle” to recreate the link with preproduction hostname. copy back the admin directory under /oracle/<SID>/102_64/network On the target. Logon as root.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 3. group : dba Use the following command to change owner and / or permission if incorrect. CRM 4.4. dbf drwxr-xr-x 2 orazc0 dba 256 Jul 12 12:20 cntrl saparch/cntrl: -rw-r----.dbf <SRC SID>arch1_2488_627747881.dbf <SRC SID>arch1_2486_627747881.orazc0 [YOU HAVE NEW MAIL] Time Navigator environment has been correctly set zc2serv:orazc0 1> cd $HOME zc2serv:orazc0 2> ls -ltr |grep sapdata drwxr-xr-x 9 orazc0 dba 256 Jul 11 10:49 sapdata4 drwxr-xr-x 8 orazc0 dba 256 Jul 11 10:49 sapdata3 drwxr-xr-x 5 orazc0 dba 256 Jul 11 10:49 sapdata2 4096 Jul 11 10:49 sapdata1 drwxr-xr-x 11 orazc0 dba zc2serv:orazc0 3> Check the restore of the mirrlog and origlog directories: CRM 4.dbf tmpinst Check the restore of the controlfiles in this tree different locations: Must match the control_files location parameter of init<SID>.dbf drwxr-xr-x 2 orazc0 dba 256 Jul 12 12:20 cntrl origlogA/cntrl: -rw-r----.dbf <SRC SID>arch1_2473_627747881.dbf <SRC SID>arch1_2480_627747881.dbf <SRC SID>arch1_2483_627747881.dbf <SRC SID>arch1_2479_627747881.0 zc2serv:orazc0 9> ls -ltr |grep log drwxr-xr-x 3 orazc0 dba 256 Jul 12 14:25 origlogA 256 Jul 12 14:25 mirrlogA drwxr-xr-x 2 orazc0 dba drwxr-xr-x 2 orazc0 dba 256 Jul 12 14:25 origlogB drwxr-xr-x 2 orazc0 dba 256 Jul 12 14:25 mirrlogB zc2serv:orazc0 10> Check in oraarch directory (you must see restored archive of source system). zc2serv:orazc0 25> cd /oracle/zc0/oraarch zc2serv:orazc0 26> ls <SRC SID>arch1_2468_627747881.dbf <SRC SID>arch1_2470_627747881.1 orazc0 dba 10665984 Nov 09 10:15 cntrlZC0.dbf <SRC SID>arch1_2485_627747881.dbf <SRC SID>arch1_2476_627747881.dbf <SRC SID>arch1_2474_627747881. DELETE or MOVE only the files.dbf <SRC SID>arch1_2481_627747881. the cntrl directory must exists ! zc2serv:orazc0 18> ls -ltr -R * |grep cntrl drwxr-xr-x 2 orazc0 dba 256 Jul 12 12:20 cntrl sapdata1/system_1/cntrl: -rw-r----.dbf BRIDGE_CRM_ECC_V2_Consistent System Refresh.dbf <SRC SID>arch1_2484_627747881.1 orazc0 dba 10665984 Nov 09 10:15 cntrlZC0.dbf <SRC SID>arch1_2482_627747881.ora You can delete those control files.dbf <SRC SID>arch1_2472_627747881.1 orazc0 dba 10665984 Nov 09 10:15 cntrlZC0.dbf <SRC SID>arch1_2478_627747881.doc Page 40/ 125 .dbf <SRC SID>arch1_2469_627747881.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh zc2serv:/>su .dbf <SRC SID>arch1_2477_627747881.dbf <SRC SID>arch1_2471_627747881. new ones will be generated latter.dbf <SRC SID>arch1_2487_627747881.dbf <SRC SID>arch1_2475_627747881. Go to /oracle/<SID>/oraarch Launch the script by using .5. Regenerating Target control files. to do it you can create the following script in /oracle/<SID>/oraarch directory: for i in <SRC SID>arch1*.. BRIDGE_CRM_ECC_V2_Consistent System Refresh.4.5. To be applied in target system.doc Page 41/ 125 .5.0 By that way..2. zc2serv:orazc0 2> lsnrctl start LISTENER_ZC0 LSNRCTL for IBM/AIX RISC System/6000: Version 10. restored archive log files should be rename to the target system name like the following: Original name: <SRC SID>arch1_<seq number>_xxxxxxxxx. Use the following command to stat the listener (“lsnrctl start LISTENER_<SID>). Oracle. check the restore of the saparch directory.dbf do newname="`echo $i | sed 's/<SRC SID>/<TAR SID> /'`" mv $i $newname echo $i done On the Target system: Logon with ora<sid> user. Starting /oracle/ZC0/102_64/bin/tnslsnr: please wait. cntrl directory should be empty. Check the result in target oraarch directory all archive log files should contain only the target SID.dbf On the target system.6.1. 3.0 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Logon to the target system with ora<sid> user. … The command completed successfully 3.2. All rights reserved.dbf New name: <TAR SID> arch1_<seq number>_xxxxxxxxx.Production on 09-NOV2007 10:53:46 Copyright (c) 1991./<script name> command. Renaming target Database.0. 2005. Rename restored archive log to target system name. Only in case of online backup used for the refresh. Check in the tree control files location that no control files are present. 3.2. 3. Starting the listener. Checking old control_files. 64bit Production With the Partitioning and Data Mining options SQL> @control.orazc0 [YOU HAVE NEW MAIL] Time Navigator environment has been correctly set zc2serv:orazc0 1> pwd /oracle/ZC0 zc2serv:orazc0 2> ls -ltr total 200 drwxrwxrwx 2 orazc0 dba 256 Jun 15 15:40 lost+found drwxr-xr-x 2 root system 256 Jun 15 15:41 920_64. . BRIDGE_CRM_ECC_V2_Consistent System Refresh. Your database is now started in NOMOUNT State. you must delete all control files.2.sql and temp.control_files='/oracle/ZC0/origlogA/cntrl/cntrlZC0. Recreating new control_files.'/oracle/ZC0/sapdata1/system_1/cntrl/cntrlZC0.ora |grep control_files *. Connected to: Oracle Database 10g Enterprise Edition Release 10. zc2serv:/>su .OLD drwxr-xr-x 5 orazc0 dba 256 Jun 25 14:41 saptrace drwxr-xr-x 64 orazc0 dba 4096 Jun 26 15:46 102_64 … drwxr-xr-x 3 orazc0 dba 20480 Nov 09 13:03 saparch drwxr-xr-x 3 orazc0 dba 4096 Nov 09 14:49 oraarch -rwxrwxrwx 1 orazc0 dba 1955 Nov 09 15:30 control.sql zc2serv:orazc0 6> as ora<sid> launch sqlplus and launch the following command to recreate control_files: @control. Check in the control_files directories if your tree control files copy are well created.sql.dbf '.sql zc2serv:orazc0 6> sqlplus '/ as sysdba'. the tree cntrl directories must be empty.doc Page 42/ 125 .0 Logon to the target system with ora<sid> user Open the init<SID> file and search for control_file parameters value: Use the following command to check control_files location parameter init oracle parameter file: zc2serv:zc0adm 3> more /oracle/ZC0/102_64/dbs/initZC0.0.dbf' If present.0 .dbf'.'/oracle/ZC0/saparch/cntrl/cntrlZC0.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.sql -rwxrwxrwx 1 orazc0 dba 208 Nov 09 15:33 temp. Logon to the target system with ora<sid> Check in $ORACLE_HOME for the two file created before (control..sql Return should be: control_files created.2. give 777 permission if it is not case. In this case oracle will apply all archive log (you will have to confirm each file) and you will have to cancel archive log application when you see the last archive log file name that you want to apply. Like described at the beginning of this doc you can find all information regarding the backup and archive log file name during (or before or after) in the SOURCE system by using DB12.5. The following message will appear: ORA-00279: change 12314918 generated at 10/31/2006 15:06:57 needed for thread 1 ORA-00289: suggestion : /oracle/QGV/oraarch/qgvdb_QGV_arch_1_2417.arc ORA-00280: change 12314918 for thread 1 is in sequence #2417 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} “press enter” First: Choose “enter” to confirm archive 1 by 1.0 SQL>Alter database mount. you need to apply at least all archive log generated on the source system during the backup. (ex: SQL> recover database until time '2006-02-01:07:11:02' using backup controlfile). BRIDGE_CRM_ECC_V2_Consistent System Refresh. Logon to the target system with ora<sid> user. The given time stamp must be 1 hour latter the last archive log generated during the backup.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 3.doc Page 43/ 125 . Using “recover until cancel” command. To do it you will have to options: Using “recover until time” command. Applying archive logs (only in case of online backup used go to the next chapter in case of offline backup).” Launch: CRM 4. like that you can check each archive log file (there should be not a lot of archive to apply because of few system activity during the backup). before opening the database. In this case you will specify a time stamp (should be at least one hour after the end of the backup) and the database will be recovered until this time. SQL> recover database until time ‘YYYY-MM-DD:HH:MN:SE’ using backup controlfile. Launch sqlplus with command “sqlplus ‘/ as sysdba’. In case of online Backup.3. Procedure. or by searching into the *. it will be the last applied archive.anf backup log file into sapbackup directory. '/oracle/<TAR SID>/sapdata1/system_1/cntrl/cntrlQGV.0 Choose “CANCEL” when the last needed archive was applied and before apply the next one.dbf). Rename the Database. Displaying the source global name : BRIDGE_CRM_ECC_V2_Consistent System Refresh. Checking-Deleting old Controlfiles and old Archive logs files on target system.5. Open the init<SID>.6. 3. Database altered.arc ORA-00280: change 12314918 for thread 1 is in sequence #2417 Specify log: {<RET>=suggested | filename | AUTO | CANCEL} CANCEL Media recovery cancelled.ora|grep cntrl *. Opening Database.dbf' Delete the old controlfiles relative to the SOURCE SID or the one that you have renamed before (ex : cntrlPGV. '/oracle/<TAR SID>/saparch/cntrl/cntrlQGV.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.dbf'.ora to get the path of the controlfiles: qg2serv:oraqgv 24> more $ORACLE_HOME/dbs/init<TAR SID>. 3. Opening the database : SQL> alter database open resetlogs.) this is the same except that the system will apply all apply until the last one (by asking for confirmation for each of them).LLLLLLL /oracle/<TAR SID>/oraarch detelte all archive log (of course your database was already opened in preceding chapter) 3. SQL> recover database until cancel using backup controlfile.sql”) SQL> @tempfiles.5.sql Database altered. ORA-00279: change 12314918 generated at 10/31/2006 15:06:57 needed for thread 1 ORA-00289: suggestion : /oracle/QGV/oraarch/qgvdb_QGV_arch_1_2417.4.5.doc Page 44/ 125 . Delete all archive logs contained in the oraarch directory. Media recovery cancelled mean that archive were successfully applied !! If using other command (recover database until cancel using backup controlfile.control_files='/oracle/<TAR SID>/origlogA/cntrl/cntrlQGV. the only remaining files should be the active controlfiles. Creating the new tempfiles : (using the script created “temp.dbf'.5. BRIDGE_CRM_ECC_V2_Consistent System Refresh. SQL> drop user OPS$ORA<SRC SID> cascade. Connect to the database : zc2serv:/>su . 3. the database PGV has been restored and renamed in QGV. Displaying the source OPS$ Users declared on the database : SQL> select username from dba_users where username like '%OPS$%'. Droping the source OPS$ users : SQL> drop user OPS$<SRC SID>ADM cascade. GLOBAL_NAME -------------------------------------------------------------------------------<SRC SID>.orazc0 zc2serv:orazc0 1> sqlplus '/ as sysdba'.0 SQL> select global_name from global_name.7. User dropped. Rename the global name (<SID>.WORLD Source SID.WORLD): SQL> alter database rename global_name to <TAR SID>.5.doc Page 45/ 125 . Recreate the OPS$ Users. Database altered. In this example. must be changed to target.WORLD. USERNAME -----------------------------OPS$<SRC SID>ADM To be dropped an recreated.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. OPS$ORA<SRC SID> To be dropped an recreated. User dropped. resource to OPS$<TAR SID>ADM with admin option.'bridg012'). Table created. Grant succeeded Recreate the table SAPUSER SQL> create table OPS$<TAR SID>ADM. Grant succeeded. User created. PASSWD varchar2(256)). 1 row created.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.SAPUSER to OPS$<TAR SID>ADM.insert.SAPUSER (USERID varchar2(256). SQL> insert into OPS$<TAR SID>ADM. zc2serv:/>su – ora<si> brconnect -u system/bridg012 -f chpass -o SAP<COMP NAME> -p bridg012 BRIDGE_CRM_ECC_V2_Consistent System Refresh. connect. resource to OPS$ORA<TAR SID> with admin option.update on OPS$<TAR SID>ADM. Note : In this way it will delete the table SAPUSER. connect. SQL> create user OPS$ORA<TAR SID> default tablespace PSAP<COMP NAME>USR temporary tablespace psaptemp identified externally. SQL> grant dba.0 Recreates the right users in accordance with the new SID : SQL> create user OPS$<TAR SID>ADM default tablespace PSAP<COMP NAME>USR temporary tablespace psaptemp identified externally. Modify SAP<COMP NAME> password (must be done for both SAPCRM And SAPECC° . Give the right authorizations to oracle users: SQL> grant dba. Grant succeeded. SQL> grant select.SAPUSER values ('SAPECC'.doc Page 46/ 125 . User created. Give authorization to OPS$<TAR SID>ADM user to modify the table SAPUSER. ddlog. truncate table SAPCRM.sdbap. truncate table SAPECC.doc Page 47/ 125 .pahi. truncate table SAPCRM.sdbar. truncate table SAPCRM.alconseg. Creating the spfile Restarting the DB. truncate table SAPCRM. truncate table SAPECC. truncate table SAPCRM.2. truncate table SAPECC. SQL> connect sapcrm Enter password :bridg012 Connected Check this result. 4. truncate table SAPCRM.osmon. 4. zc2serv:/>su . Oracle tasks.1.dbsnp.moni. truncate table SAPECC. truncate table SAPCRM.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.dbstatiora. truncate table SAPECC. Create the new target spfile. truncate table SAPCRM.orazc0 zc2serv:orazc0 1> sqlplus '/ as sysdba'.dbstathora.dbstattora.tpfet.ddlog. Stoping the DB. truncate table SAPCRM. Post copy. truncate table SAPCRM. BRIDGE_CRM_ECC_V2_Consistent System Refresh. truncate table SAPCRM.dbstaihora.0 4.alsystems. truncate table SAPCRM.sdbah.tlock. Truncate the following tables: Must be done for SAPECC and SAPCRM.tpfht.sdbad. truncate table SAPCRM. truncate table SAPCRM. Deleting the unusable entries in SAP tables : Connect to the DB wih the SAP user (SAPCRM / SAPECC users). 3. Database dismounted. Creating new spfile. SQL> create spfile from pfile. Stopping the DB. File created. SQL> shutdown immediate Database closed. ORACLE instance shut down. Database closed. Turning OFF the archive log mode.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Starting-up the Database in mount mode : SQL> startup mount. ORACLE instance started. ORACLE instance shut down.0 SQL> shutdown immediate. Database opened. Database dismounted. Turn off the archive log mode : 745184 bytes 1241513984 bytes 1174405120 bytes 1323008 bytes BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 48/ 125 . SQL> startup Staring up and opening DB. Connected. 4. Total System Global Area 2417987296 bytes Fixed Size 745184 bytes Variable Size 1241513984 bytes Database Buffers 1174405120 bytes Redo Buffers 1323008 bytes Database mounted. Stopping the Database: zc2serv:/>su . Total System Global Area 2417987296 bytes Fixed Size Variable Size Database Buffers Redo Buffers Database mounted.orazc0 zc2serv:orazc0 1> sqlplus “ / as sysdba”. ORACLE instance started. Otherwise the new ECC and CRM system may start to send messages to the old CRM and ECC system directly after startup.4 BRIDGE_CRM_ECC_V2_Consistent System Refresh. There is an additional step to be executed before the startup of the SAP new systems. Database log mode Automatic archival Archive destination Oldest online log sequence Current log sequence No Archive Mode Enabled /oracle/QGV/oraarch 2387 2390 4.doc Page 49/ 125 . Database altered. Here we will have to re-import the Source RFC Destination exported in step 2.4. Change the hostname or IP to something silly (e. Re-importing RFC destinations table content. to the word “dummy”) using an SQL-command for each RFC destination between ECC and CRM (see example below). In ECC you have change all entries containing the hostname or IP of the CRM system. Check the archive log status : SQL> archive log list.4.4. Creating the import parameter file.g. Opening the Database: CRM 4. Logon to the target system with <sid>adm user.0 SQL> alter database open.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh SQL> alter database noarchivelog.4. FILE='sm59_ZR0. in CRM vice versa. The old hostnames of ECC and CRM saved in the RFC destinations must be changed in field RFCOPTIONS of table RFCDES on database level. Go to /oracle/<SID>/sapreorg Use “vi” tools to create a “import_RFC. After that the new systems can be started. Database altered.dat' File created in Step 2.sql” file like the followings: IMPORT CLIENT=000 Client is not important there because RFC tables are client-independent ones. sql" [New file] IMPORT CLIENT=000 FILE='sm59_ZR0.sql "import_rfc. As <sid>adm Command: “R3trans -w import_sm59.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.sql” The warning is due to the fact the Source system = target system (normal).dat' Launching the Data import.log file if you don’t have any other error. Use the following command to launch the table import.log import_rfc.doc Page 50/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 zr2serv:zr0adm 4> vi import_rfc. Check in the log file that you don’t any error during the table import. check in import_sm59. Stopping Oracle database. Post Copy: SAP tasks [CRM – ECC] 5. Execute the saplicense program to get the Hardware key : qg2serv:qgvadm 5> saplicense -get saplicense: HARDWARE KEY = A0121256785 Then.sap-ag.. Now you will have to completely stop oracle database (before re-starting it with <sid>adm and startsap command).0.4 LICENSE_KEY = KTA8FOLK975PXNYN6F2VPLBL (license key given in sapnet for this system) saplicense: License successfully installed 5. Launch sqlplus: zc2serv:orazc0 1> sqlplus ‘/ as sysdba'..0 5.. Database dismounted.de/notes -> License Keys -> my SAP Business Suite + Display license keys requested by me.5. ( https://websmp101.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.. SQL> shutdown.2.0. Log-on to the target server with ora<sid> user.. Log on the target system as <sid>adm. Connected to an idle instance. or search for the source SID) qg2serv:qgvadm 6> saplicense -install Specify your SAP System ID: SAP SYSTEM ID = <TAR SID> Specify your unique System idenfification: If you have no systemnumber specified just press enter...0.. Database closed.5. ORACLE instance shut down.. Re-Install SAP License [CRM – ECC]. install the key. wich has been already declared under sapnet. Oracle. SYSTEM-NR = 000000000310461520 (System number register in sapnet) Specify your hardware key: HARDWARE KEY = A0121256785 (result of the command saplicense –get) Specify your installation number: INSTALLATION NO = 0020200711 Specify your expiration date: EXPIRATION_DATE [YYYYMMDD] = 99991231 (enter YYYYMMDD as a date) Specify your license key: LICENSE_KEY 1.Production on Wed Nov 21 12:50:32 2007 Copyright (c) 1982.1. SQL*Plus: Release 10.. BRIDGE_CRM_ECC_V2_Consistent System Refresh. All Rights Reserved.doc Page 51/ 125 ..0 .2.. 2005..2. Leave oracle user Logon with SAP user <sid>adm Start sap system (and oracle)...AIX v6.0:20 /oracle/ZC0/102_64/bin/tnslsnr LISTENER_ZC0 inherit orazc0 1429684 6058138 1 12:52:51 pts/0 0:00 grep LISTEN oraz10 1548400 1 0 Nov 16 .log ZC0 database started /usr/sap/ZC0/SYS/exe/run/startdb completed successfully Checking ZC0 Database -----------------------------ABAP Database is running Starting SAP Instance DVEBMGS00 BRIDGE_CRM_ECC_V2_Consistent System Refresh.4. zc2serv:orazc0 6> logout zc2serv:/>su . check if oracle listener is well started (you must see both listener (java and abap ones).11..zc0adm Time Navigator environment has been correctly set zc2serv:zc0adm 1> startsap Checking ZC0 Database -----------------------------Starting SAP-Collector Daemon -----------------------------13:41:05 21.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.55 5L-64 bit 060323 * Usage: saposcol -l: Start OS Collector * saposcol -k: Stop OS Collector * saposcol -d: OS Collector Dialog Mode * saposcol -s: OS Collector Status * The OS Collector (PID 1110062) is already running .. ************************************************************************ saposcol already running Running /usr/sap/ZC0/SYS/exe/run/startdb Trying to start ZC0 database .0.0 .2.2.doc Page 52/ 125 .64 bit Production With the Partitioning and Data Mining options zc2serv:orazc0 4> ps -ef |grep LISTEN orazc0 1138908 1 0 Nov 16 .. SQL> exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.3. Be sure for RFC destination that the hostname contained in table RFCDES was correctly re-imported in step: 4.0 Now. Log file: /sapmnt/ZC0/home/startdb..2007 LOG: Effective User Id is root *********************************************************************** * This is Saposcol Version COLL 20.0:06 /oracle/Z10/102_64/bin/tnslsnr LISTENER_Z10 inherit 5.90 640 . Re-Starting SAP (and Oracle) instance [CRM – ECC]. Then ‘Execute’. 5. Launch se38 and execute the RADDBDIF program in background mode. On the refreshed system (target).2.log Instance on host zc2serv started IGS on host zc2serv started CRM 4.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh -----------------------------Startup-Log is written to /sapmnt/ZC0/home/startsap_DVEBMGS00. Use the “extras” menu to distribut the configuration.4. in client 000 with user DDIC.0 5. Go to Menu Overview Systems.4. as DDIC and in English. RADDBDIF program. Source system of database copy <SRC SID> Change originals from <SRC SID> to <TAR SID> ? Yes.doc Page 53/ 125 . Choose ‘Database copy or Database migration’. Launch SE06 to reinitialize the transport system. 5. in English language and with user DDIC. TMS Re-configuration. Launch STMS transaction. On the Transport Domain Controller. You must check which system is the transport domain controller (normaly production system for a preproduction system refresh) in your transport domain. Transport System Re-configuration (TMS) [CRM – ECC]. Logon to the target system in client 000.1. Suppress the refreshed system.4. Logon the domain controller system in English. Logon to the target system in client 000. BRIDGE_CRM_ECC_V2_Consistent System Refresh. And answer ‘Yes’ on all the next pop-ups : Do you want to reinstall the CTO ? Yes ‘Single system settings set’. Confirm the first popup. Do you want to delete old versions of the transport routes ? CRM 4. and use SAP System Check Transport Directory Result should be like the followings. Delete old versions of the transport routes ? Yes. save . In this step you will re-import the SAP profiles which are only stored on file system.0 Yes.5. 5. Re-import SAP instance profiles [CRM – ECC]. After the SE06.doc Page 54/ 125 .5. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Then go to Overview Systems. Log on the domain controller as DDIC in client 000 and in English and accept the new system <TAR SID> waiting in « STMS overview systems » by using STMS transaction.1. Delete TMS configuration ? Yes. Deleting the old profile on the target system. Use RZ10 to delete the source system profile present in target database.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Change originals from <SRC SID> to $news$? Yes. !!! Be sure to answer « NO » when asking to delete profile at operating system level. Do you want to delete the TMS configuration ? Yes. go back and launch STMS again (as the indications in the message at the bottom of te screen at the end of the SE06) You are asked to register in the domain « DOMAIN_<TMS domain controller SID> ». Use Menu Profile Delete All Versions Of a profile. Select the SAP System. 5. Checking the transport system: launch STMS. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 5.0 Use RZ10 to reimport the right profiles. reaffect the operation mode to the corresponding time period in the SM63. to TEST : BRIDGE_CRM_ECC_V2_Consistent System Refresh. Then choose: Menu Settings Based on actual status New instances Generate. Set the Client details like before the resfresh. use SE06 to set the system to “Not Modifable”. When the Destinations have been created. Re-importing exported users [CRM – ECC]. Operation Mode configuration [CRM – ECC]. Choose According to the original configuration.2. Importing right profiles CRM 4. Use SCC4 Tcode to change the role of the reference Client. Deletes all entries making reference to the source system. Re-importing logical system definition [CRM – ECC]. Use the tcode RZ04 to restore operation modes like before the refresh (check in step 0).6. Use: Utilities -> Import Profiles -> Of Active Server 5.8. The server name has to be the same than RZ04. 5. using SCC4 tcode and accordingly with the screenshots made in step: 0 5. like the followings: Select the hostname and then : Check also the RZ03 tcode.7.doc Page 55/ 125 .5. Use STMS to re-import all logical destination exported in step: 0 Launch BD54 to check. 9.9. The protection level of the target client has to be 0. 5. you have to make the following steps: Connect to the first instance and start transaction SMT1 Select R/3 systems and click create button - Enter the trusted destination and click enter - Log on to the target system BRIDGE_CRM_ECC_V2_Consistent System Refresh. Do the following to check and /or recreate. recreate needed Thrusted RFC destination (thrusting ECC is mandatory for CRM). To configure the trusted relationship between two SAP instances. Use SMT1.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 Check the client copy Protection.4. compare with screenshots taken before the refresh. Execute STMS or SCC9 Tcode to Import the transport order exported at the step 2. Execute the Post operation using SCC7 tcode. Check / Recreate Thrusted RFC destinations [CRM – ECC].doc Page 56/ 125 . 5. Depending of the project need.doc Page 57/ 125 . Locking project users [CRM – ECC].10.0 - Repeat the steps in the other SAP system Finally you can check the trusted destinations via SM59. you can now lock all final user to avoid connection on the system before the end of the refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Check the entries and save CRM 4. First use SU10 to display the current locked users (to be saved in a file). BRIDGE_CRM_ECC_V2_Consistent System Refresh. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. WEBADMIN. you own user. CUA_ADM_BATCH. Let the selection empty. ALEREMOTE. ADMINSAP. SOLM*…. SM_TRUSTED. OMS_FAX. BATCH_STDJOB. OMS_RFC. WF-BATCH. SAPCPIC. RFC_<CRM SID>_CLNT. Select the user to lock (except the exception listed below). WEBLOGIN. Use SU10 to select all user except the followings (normaly all technical users should have the user group “SUPER” affected. OMS_ADMIN. SPOOL_ADM.doc Page 58/ 125 . TMS_ADM. BRIDGE_CRM_ECC_V2_Consistent System Refresh. CUA_ADM. DDIC. CRM_<SID>_<CLNT>. CONTROLM. like that it will be easy to select those users with one group): SAP*.0 Save the following user list in a file to be sure to not unlock them when the refresh (locked users before the refresh must remain locked after the refresh !). IPCUSER. RFC_<ECC SID>_CLNT. SAPJSF. CSMREG. 11.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Result should be like the followings for TST01 and TST03 tables.doc Page 59/ 125 . 5. If inconsistencies are detected. Choose: Menu Temse Data Storage Consistency Check. Checking the TEMSE Consistency [CRM – ECC] Use SP12 and perform a consistency check of the TEMSE. delete them. You will have to unlock those users before delivering the system to the users. BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 Select the user to be locked and choose “lock”. Launch transaction SPAD in change mode. BRIDGE_CRM_ECC_V2_Consistent System Refresh.12.13.doc Page 60/ 125 . You have to delete source system licenses. delete it : 5. Choose button “output devices”. check cluster installation document in case of problem) for node 1 and 2.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 5. Launch transaction SLICENSE First select the <source system> license to be deleted : Then. Re-import Printer Definition using SPAD. Deleting unuseables SAP licenses [CRM – ECC]. because hardware key are different on both. one for each cluster node. for cluster system (like pre-production) be sure to have installed both licenses (should be 2 license installed. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Choose Menu Edit Transfer Import.doc Page 61/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh. CRM 4.0 Make the following selection. Check the log and check the printer in SPAD. doc Page 62/ 125 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 5. check in the column for harcoded SID’s (Use transaction to change them back if you’ve found some). BRIDGE_CRM_ECC_V2_Consistent System Refresh. Check the physical Path definition.0 Use the “import” button. 5.15.14. Launch transaction SPAD. Launch SE16 Make the following selection You must check only parameters for hostname or SID. double click each spool and compare with your screen shots. Make the modification to be sure you are in the same configuration than initial. CRM 4. Re-import Spool servers Definition using SPAD. After importing. Browse table PATH with SE16 transaction to check if some physical path are containing SID or hostname hardcoded (normaly no). Go to “spool servers”. 16. Changing SAP Directories.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 63/ 125 . Change to the target SID. A new directory will be added. look for directories containing the source SID select the directory press “configure” Modify the Directory Name with the target SID. but the old one still appear. - select the old directory press “configure” then delete it BRIDGE_CRM_ECC_V2_Consistent System Refresh. All directories should no point to target system Use AL11. Save and go back.0 5. execute a Diagnostic for cyclic CCMS system programs. Menu SMLG Goto System diagnosis Cyclic syst prog . Result should be “No problems Found”.19. Checking SAP Help. Go to the PlainHtmlHttp tab and check the presence of a variant : CRM Help: BRIDGE_CRM_ECC_V2_Consistent System Refresh. [CRM – ECC] Use SR13 to check that the SAP Help is declared and available.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.18.doc Page 64/ 125 . For logon groups. Use the SMLG to recreate the logon group.17. If the jobs are not scheduled. Use the RZ12 to reaffect the different application servers to a particular RFC Server Group. Checking the system settings [CRM – ECC] Use SE06 tcode to Check the System Change Option : The system status has to be “Not Modifiable” : 5. Select the server + ALLOW 5.0 5. Restoring logon group and RFC server group [CRM – ECC] Use the screen copy made in section 0 to restore logon group with SMLG and RFC server group with RZ12. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 ECC Help Check the SAP Help : The help should be displayed in a Internet Explorer windows. 5.20. Checking SAPNET Connection using SNOTE [CRM – ECC]. First, set the system status to modifiable in SE06 (don’t forget to close it after the check) Use SNOTE and download a factice note to check the connection : BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 65/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 Connection is OK. 5.21. Checking / Changing IGS RFC destination [ECC only]. Execute SM59 and modify the RFC Destination IGS_RFC_DEST (TCP/IP connections) In the field program ID, replace the <SRC SID> (IGS.<SID>) by <TAR SID> Save the modification, and test the connection. Then, execute RSRT to do an IGS Test (This check has to be done on each instances) : Select to test the display. Result should be like the followings. BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 66/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 5.22. Restoring SLD data connection. [CRM – ECC]. You must restore all SLD data information referring to the screen shot made in step 0 launch SLDAPICUST The fields “Host Name” and “Port” has to be filled for the right SLD. Use SLDCHECK to check the connection to the System Landscape Directory by the internet browser. Use RZ70 to check the background job scheduling. Check hostname and service name for SLD Bridge. BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 67/ 125 you may want to delete entries. every client] In every pair of ECC and CRM clients connected to each other. XI. For each destination make a connection and authorization tests (trusted destination should work too). SOLMAN and SRM destination (all should work. you can check in screen copy made before the export in case of problem). Converting logical system names is described in section 6. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Do not perform the logical system conversion (BDLS) before all qRFC queues are emptied as described in section 6. 6. Vice versa in the ECC system the RFC connections named after the logical system names of the clients of the source CRM system should now point to the host of the new ECC system. 6. If other entries cannot be processed.4. try to solve the problem. In any case it is important that all the queues be empty (as shown on the screenshots) before proceeding with the next steps.0 5. If there is no other possibility.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. they all have to be processed. you will have to check if they works (make special attention for ECC. If that is not the case.2 of this document. adjust the connections. Check old RFC destinations [ECC and CRM] The RFC destinations in CRM named after the logical system names of the clients of the source ECC system should now point to the host of the new ECC system. Middleware reconfiguration [CRM – ECC]. Important: Never change these RFC destinations to point to the hosts of source systems again. use transaction codes SMQ1 for outbound and SMQ2 for inbound queues to check if these queues still contain entries.doc Page 68/ 125 . Checking RFC Destination [CRM – ECC] RFC destinations on target system should be re-imported in section 4.1 6.2. If they do. because otherwise the system may immediately start sending messages to the wrong systems! This is why these hostnames had been re-imported (exported before the copy) before initially starting the systems.23. Process Entries of qRFC queues [ECC and CRM. This way we will be able to process all the entries remaining in the qRFC queues. BW. Postpone the connection to the central user administration until the logical systems have been converted (CUA reconnexion is described in step: 8. although this will lead to data inconsistency (which will maybe be feasible in a test or training system).4 (BDLS) of this document.1. You can just delete queues called CRM_SITE_* as they refer to mobile clients. create them. are not locked and have the password that is configured in the RFC destinations mentioned below! System ECC CRM CRM CRM Username RFC_<CRM-SID>_<CRM-CLIENT> RFC_<ECC-SID>_<ECC-CLIENT> RFC_<CRM-SID>_000 WF-BATCH Profile SAP_ALL SAP_ALL SAP_ALL SAP_ALL Used for Connection CRM -> ECC Connection ECC -> CRM Replication and Realignment Workflow Check if all the RFC destinations ECC and CRM exist for every pair of clients connected to each other. Type R/3 R/3 Log. every client] Check if all the technical users for RFC communication between ECC and CRM still exist for every pair of clients connected to each other.doc Page 69/ 125 . create them. System ECC CRM CRM CRM Target CRM ECC Name like logical system name of CRM target client like logical system name of ECC target client SAPCRM_MW_RR_<CRM-target-client> WORKFLOW_LOCAL_< CRM-target-client > User ID RFC_<ECC-SID>_<ECC-client> RFC_<CRM-SID>_<CRM-client> RFC_<CRM-SID>_000 WF-BATCH BRIDGE_CRM_ECC_V2_Consistent System Refresh. If not.3.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. If not.0 6. Log. Especially check that all the user IDs exist. Check RFC destinations in the target systems [ECC and CRM. As it is not possible to do authorization checks for logical RFC destinations. this is a good chance to ensure that the correct password is set in the workflow destination.doc Page 70/ 125 . Make sure that all RFC destinations work. Navigate to Maintain Runtime Environment → Configure RFC Destination in the tree structure. right click on Configure RFC Destination and choose Execute Activity. also if it already exists. Enter user ID WF-BATCH and the password you entered in section 6.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. The RFC destination for the workflow should be created using transaction code SWU3. BRIDGE_CRM_ECC_V2_Consistent System Refresh.3 (see screenshot below). Open the RFC connection in change mode and choose Destination → TRFC Options from the menu and configure 10 Connection Attempts up to task and one minute Time between retries (see screenshot below).0 Additionally you must check the TRFC options for the two connections of type R/3. You will receive an error if the password you enter is wrong. once in ECC and twice in CRM: • • • • • In the ECC system. you have to uncheck both Test Run and Check Existence of New Names in Tables. To actually perform the conversion.2). enter the old and new logical system names and select Conversion of Client-Dependent and Client-Independent Tables. BRIDGE_CRM_ECC_V2_Consistent System Refresh. every client] In every pair of clients connected to each other both in the ECC and CRM system. In the ECC system. Ignore this warning but pressing Enter on your keyboard. convert the name of the ECC source system / client to the name of the ECC target system / client. all tables in the target clients containing the logical system name now still contain the logical system name of the source clients.) It is important that all the qRFC queues are empty before converting the logical system (as described in section 6. convert the name of the CRM source system / client to the name of the CRM target system / client. Important: If the specified new logical system name already exists in the system.4.doc Page 71/ 125 . convert the name of the BW source system / client to the target BW target system / client. Logical System Conversion (BDLS) [ECC and CRM. you will receive a warning. Check in the Landscape Detailled design file if there is some other system connected and you need to convert them. In the ECC system. CRM 4. These entries have to be converted now. Call transaction code BDLS. In the CRM system. In the CRM system.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 6.0 You have to perform the logical system conversion three times per pair of clients. convert the name of the ECC source system / client to the name of the ECC target client. (This is called logical system conversion. convert the name of the CRM source system / client to the one of the CRM target system / client. check for the Logical systems (should be changed by BDLS) in accordance with the screenshots . grant the role SAP_BC_CUA_SETUP_CLIENT to distribute the CUA model. (If not.doc Page 72/ 125 . call transaction code BD64 and select the desired model view’s name. and click Edit → Delete. choose Distribution model → Switch to processing mode in the menu.0 Optional: After the logical system conversion finished.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.g. (Call transaction code BD64 in the target clients.) After that. Make the user ID used to logon to the target systems (as entered in the RFC destinations) is authorized to distributed the model in every target system.5. you might want to run report ZSCAN_LOGSYS_WAS from SAP note 564435 in both systems to check for tables still containing the old logical system name. delete all the distribution models that will not be used in the target system’s clients (but only in the source system’s clients) both in ECC and CRM systems. you can e. Choose Edit → Model View → Distribute from the menu. Finally re-distribute all ALE distribution models used in the target clients from the system and client where they were defined. see section 0. BRIDGE_CRM_ECC_V2_Consistent System Refresh.) 6. select the desired model view’s name. Follow the instructions in SAP note 564435 on how to check the logical system conversion on what to do if the old logical system name is still found. Logon to the defining system. deselected all systems except the ones you refreshed and start the distribution. Edi port and partner profile [ECC – CRM] Use the transaction WE20 and WE21 to check and modify the Port Definition and the Partner Profiles (Partner Type LS. 6.doc Page 73/ 125 . Adjust the entry for the connected CRM system in the table CRMRFCPAR as shown in the screenshot (using transaction code SM30). every client] Check that CRM is marked active in table CRMSONSUM.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Apply Middleware Settings [ECC.0 6. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Apply Middleware Settings [CRM. Call transaction code SMOEAC in the CRM target client. every client] If every CRM client connected to an ECC client check if the values from table SMOFPARSFA contain the correct RFC destinations (using transaction code SM30). These are the most important rows: Key CRMCFSOLTP CMRCREDCHE R3A_COMMON CRMGENERAL MKTPLBW MKTPLSEM Parameter Name CRMCFSOLTP CMRCREDCHE CRM_DEFAULT_DESTINATION LOGICAL_SYSTEM MKTPLBWRFC MKTPLSEMRFC Parameter Value 1 RFC destination to connected ECC target client RFC destination to connected ECC target client RFC destination to connected ECC target client Logical system name of CRM target client RFC destination to connected BW client RFC destination to connected BW client CRM 4.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 6. this value had not been customized in the source client and there is no need to change anything.0 The ECC site has to be updated in every CRM client. Confirm by clicking the green hook and do not forget the save your settings using the disk button. After a system refresh the mobile sites usually should be deleted and recreated for the new laptop to be connected. display it by double-clicking on its name (usually OLTP) and switch to change mode (e. If the value is <ENTER DESTINATION>. select object type site and press the goggles button display the sites.7.g. by pressing F9). Press the button Site Attributes. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Choose the new RFC destination for the connected ECC target client and click the Get Values button to update the logical system name. They should have been converted during logical system conversion. Navigate to the ECC site.doc Page 74/ 125 . If everything is working.199..2" Java(TM) 2 Runtime Environment.0 For every client click the Edit Client button and check connection data: client number. J2RE 1. Click on the entry for your system in the list on the top of the right-hand side of the database screen to display the configured clients.90:0.0 Using JAVA_HOME: /usr/java14_64 Using JVMOPTIONS: -Xrs Using CLASSPATH: .. Mark the connection as Default and the use the Log in button to test the connection. Press the OK button to confirm. Enter the command “cd $IPC_HOME/BIN.jar:./ lib/iaik_jce./admin.8../lib/iaik_ssl. CRM 4./lib/IPCPatch.sh”.0 icserv:ipcic1 3> cd $IPC_HOME/bin.sh Using DISPLAY: 10.2) Classic VM (build 1./admin.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142-20060421 (SR5) (JIT enabled: jitc) Click on Next twice in the IPC administration tool window to get to the database screen.jar:.doc Page 75/ 125 .33./lib/thirdParty.4.199.zip:.4. logon to the operating system of the CRM central instance server as user <crm-sid>ipc./lib:.jar:. you will not receive any message and the Log in button will be grayed out./lib/IPCExt. Setup IPC Connection for the CRM target system [for every client] To call the IPC administration tool.jar:. Set the DISPLAY environment variable to your local desktop computer and ensure it can display X-windows (by running an X-server software like Hummingbird Exceed).4./lib/IPCCustPatch.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 6.4. ..jar AIX icserv 3 5 00C9B44E4C00 java version "1. BRIDGE_CRM_ECC_V2_Consistent System Refresh. icserv:ipcic1 1> whoami ipcic1 icserv:ipcic1 2> setenv DISPLAY 10. user ID (usually IPCUSER). .90:0.. Otherwise you will receive an error message..jar:. Standard Edition (build 1.jar:. and password..2./lib/classes12./lib/S AP_IPC..33.. 0 To check if the CRM server can connect to the IPC server. call transaction code SE37.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. To start an IPC session. login the CRM system with an administrative user (any client). BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 76/ 125 . enter the name of the function module com_ipc_session_begin and press F8 to start it. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Repeat this for all clients connected to IPC.) 6.java customerexits. and the export parameter EV_SESSION_ID_IPC must not be empty.class YYPricingUserExits.doc Page 77/ 125 .0 Enter the number of a CRM target client for import parameter IV_CLIENT and any string for import parameters IV_USER_NAME and IV_USER_LOCATION and press F8 again to execute.9. Customer customizing is contained in user exit files: • • • YYPricingUserExits. (You can check all the clients from any client.properties Those files have to be copied from source to target system. YY* Files are located in “/usr/sap/<IPC SID>/ipc/lib/userexits”: BRIDGE_CRM_ECC_V2_Consistent System Refresh. There must not be any error. Updating IPC customizing configuration files. class 00:00 YYPricingUserExits.1KB/s Logon to target server and change the files owner to <tar sid>adm:sapsys Customer exits File are located in /usr/sap/: Copy “customerexits.properties <user>@<tar host>:/usr/sap/<IPC SID>/ipc/lib/ ebp7096@q15serv's password: xxxxxxx customerexits.1KB/s 100% 20KB 20.java 00:00 • 100% 20KB 20.0 Copy “YY*” files from Source server directory to same directory on target host (use “scp” command) : Source files are located in /usr/sap/<SRC SID>/ipc/lib/userexits Use the followings: • Logon to source server (IPC is on linux server for project evts before upgrade to V2) and go to: <src server>:/ # cd /usr/sap/<IPC SID>/ipc/lib/userexits <src server>:/usr/sap/<IPC SID>/ipc/lib/userexits # <src server>:/usr/sap/<IPC SID>/ipc/lib/userexits # scp YY* <user>@<tar host>:/usr/sap/<IPC SID>/ipc/lib/userexits ebp7096@q15serv's password: xxxxxxx YYPricingUserExits.properties • 100% 547 0.5KB/s 00:00 Logon to target server and change the files owner to <tar sid>adm:sapsys BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.properties” files from Source server directory to same directory on target host (use “scp” command) : Source files are located in /usr/sap/<SRC SID>/ipc/lib/ Use the followings: • Logon to source server (IPC is on linux server for project evts before upgrade to V2) and go to: <src server>:/ # cd /usr/sap/<IPC SID>/ipc/lib/ <src server>:/usr/sap/<IPC SID>/ipc/lib/ # <src server>:/usr/sap/<IPC SID>/ipc/lib/ # scp userexits.doc Page 78/ 125 . CRI*.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. call transaction code SMQR in the CRM target client. enter the logical system name of the ECC target client as queue name. and click the green hook. To register the qRFC inbound queues needed for communication with ECC or mobile clients and for CRM internal processing (R3A*. The steps of the section will have to be repeated in every CRM client connected to an ECC client. CRM*.doc Page 79/ 125 . call transaction code SMQS in the CRM target client.0 6. and CRI*. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Repeat this step similarly for queues R3A*. You cannot register queues for a client different from the one you are logged on to. every client] Important: Now qRFC inbound and outbound queues have to be registered. Register qRFC-Queues and Test Initial Downloads [CRM. and CSA*). To register the qRFC outbound queue for sending messages to the ECC. Click the Registration button.10. Click the Registration button. enter CSA* as queue name and click the green hook. set MAXCONN to 10. CRM*. Make sure that this queue is marked type N after this. After that exclude this queue from the schedule by choosing Edit → Exclude from the menu and enter its name.doc Page 80/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh. and confirm using the green hook. click on the Register button. the queue SAPCRM_MW_RR_000 has to be registered at the QOUT scheduler.0 To enable replication and realignment. Call transaction code SMQS in the CRM target client. set destination to SAPCRM_MW_RR_000 and MAXCONN to 1.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. enter the logical system name of the CRM target client as queue name. Call transaction code R3AS. Call transaction code SMQS in the ECC target client. click the Registration button. and click the green hook. To test the connection the ECC system.0 Register the qRFC outbound queue for sending messages to the CRM target client from ECC. OLTP as source site and CRM as destination site. enter DNL_CUST_BASIS as load object. set MAXCONN to 5. BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 81/ 125 . Start the download by clicking the green hook with the clock.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. you should perform an initial download of a customizing object. (There is another administration procedure on that subject. enter *CUST* as load objects. Check if the download was successful using transaction code R3AM1. Again call transaction code R3AS.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. every client] Check if all middleware jobs are running properly in every CRM client using transaction code SMWP. Start the download by clicking the green hook with the clock. Check Middleware Jobs [CRM.0 Finally download all customizing objects from the CRM online database into the CRM consolidated database (CDB) for CRM mobile. 6.doc Page 82/ 125 .11. BRIDGE_CRM_ECC_V2_Consistent System Refresh. CRM as source site and CDB as destination site.) Finally restart the middleware queue daemon using transaction code SMOHQUEUE by pressing the Start Queue Daemon button. Manual Post Processing 6.2.12.1. UI_CFG_BRIDGE) 6.doc Page 83/ 125 .12.12.0 6. Set RFC Destinations and URLs System: CRM Procedure: SAP CRM Transaction code IMG path Set RFC Destinations and URLs SPRO Customer Relationship Management Basic Functions Configuration Engine Set RFC Destinations and URLs Check what are the target destinations defined in this transaction (eg UI_ANALYSIS_BRIDGE.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Define URLs System: CRM Procedure: SAP CRM Transaction code IMG path Define URLs SPRO Customer Relationship Management Configuration Engine Define URLs Basic Functions For each target destination in the previous transaction. the URL has to be changed to call the correct IPC server: BRIDGE_CRM_ECC_V2_Consistent System Refresh. do http://<IPC server>:<port> /csr/csr/init. Data Exchange Conditions (ECC5) System: Procedure: ECC5 SAP CRM Transaction code IMG path Data Exchange Conditions SPRO Integration with Other SAP Components Customer Relationship Management Basic Functions Data Exchange Conditions For ZCNP and ZSPA condition types.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh UI_ANALYSIS_BRIDGE UI_CFG_BRIDGE UI_CSR http://<IPC server>:<port>/ipcpricing/ http://<IPC server>:<port>/ ipc/ipc/command.do CRM 4.3.doc Page 84/ 125 . the CRM logical system has to be changed after a client copy: 6.12. Distribution Model Maintenance (ECC5) System: Procedure: ECC5 SAP CRM Transaction code Maintain Distribution Model and Distribute Views SALE or BD64 BRIDGE_CRM_ECC_V2_Consistent System Refresh.4.0 6.12. doc Page 85/ 125 . 4. Save the distribution model: BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh IMG path CRM 4.0 IDoc Interface / Application Link Enabling (ALE) Modelling and Implementing Business Processes Maintain Distribution Model and Distribute Views 1. Select Edit/Model view/Create using template (Ctrl + F5) in the menu and follow the program instructions.0 (Without Qualifications) HR_CRM_EMP” Save. Start transaction BD64 and go in change mode Delete the existing distribution model “HR to SRM/CRM 4. Select the appropriate CRM and ECC5 logical system: 5. 3. 2. doc Page 86/ 125 . Select the model and choose : Environment Generate Partner Profile and execute: BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 6. Maintenance of system data System: Procedure: CRM SAP CRM Transaction code IMG path Maintenance of system data EEWC - Before changes (this entry is only valid for system ICACLNT411).doc Page 87/ 125 .0 6. BRIDGE_CRM_ECC_V2_Consistent System Refresh.5.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Result: CRM 4.12. User Interface settings for IPC configuration System: Procedure: CRM IPC SAP CRM Transaction code IMG path On each new CRM server created by client.12.do 6.schneider-electric.eud. Some User Interface settings have been set for configuration in IPC XCM file.0 Copy this entry and change system = actual CRM system + logical system = actual CRM system.7. Result: 6. This file can be changed via the following URL: http://<IPC server>:<port>/ipc/admin/xcm/init.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.6.doc Page 88/ 125 .com:51100/ipc/admin/xcm/init. Assign RFC destination for synchronous Method calls System: Procedure: CRM SAP CRM Transaction code IMG path Assign RFC destination for synchronous Method calls BD97 no The trusted RFC destination for connecting to ECC5 has to be updated for BAPI calls and dialog calls BRIDGE_CRM_ECC_V2_Consistent System Refresh.12. a new IPC server is connected.do Example : http://dcserv. 8. Activation of cross system lock on ECC5 System: Procedure: ECC5 SAP CRM Transaction code IMG path Before change: CSL: Token Manager SM30 on table CSL_M no BRIDGE_CRM_ECC_V2_Consistent System Refresh.12.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 89/ 125 .0 6. Activation of cross system lock on CRM System: Procedure: CRM SAP CRM Transaction code IMG path Table CSL_M: CSL: Token Manager SM30 on table CSL_M + SM30 on table CSL_CCP no BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 Create an entry for CRM and ECC5 logical system and set CSL activated for both systems: Result: 6.12.9.doc Page 90/ 125 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. doc Page 91/ 125 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Before change CRM 4.0 Create an entry for CRM and ECC5 logical system and set CSL activated for both systems: Result: Table CSL_CCP: Before change BRIDGE_CRM_ECC_V2_Consistent System Refresh. 0 Create an entry for CRM and ECC5 logical system: Result: 6.10.12. System: Procedure: CRM Adapdation of RFC destination for ECC5 calls from CIC SAP CRM Transaction code IMG path CSL: Token Manager SM59 + EWFC0 Customer Relationship Management Interaction Center WinClient Component Configuration Visible Components Action Box BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 92/ 125 . check if the RCF destination is available.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Settings Define Configuration Profile for Action Box CRM 4. this RFC destination is client-dependant and this destination is valid for all the clients on the same CRM server. First. this RFC destination can be used. if you have several CRM clients on the same server. Sales orders).0 The trusted RFC destination RFC_CIC_REM has been created to call the ECC5 from CIC to create sales documents directly on ECC5 (eg. If not create a new one. Transaction SM59: BRIDGE_CRM_ECC_V2_Consistent System Refresh. which calls the correct ECC5 client.doc Page 93/ 125 . and you have to create one RFC destination per client. But. So. doc Page 94/ 125 .0 Transaction EWFC0: For each transaction defined in the action box. the RCF destination has to be changed: Select Action box profile that is used within your CIC Profile Press change button For the following transactions do the following changes BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. doc Page 95/ 125 .0 Position Cursor on Transaction and press button ‘Data Flow’ Change the RFC Destination to the new one Here the RFC_CIC_REM destination has to be changed in RFC_CIC_REM_225 Press Back button and save changes Repeat these steps for all the transaction defined in the action box ! BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. 12.doc Page 96/ 125 .11. System: Procedure: CRM Check/Correct table SMOFPARSFA SAP CRM Transaction code IMG path Middleware parameter SM30 on table SMOFPARSFA none This table which pilots the middleware has to be reviewed and all the RFC destination has to be checked.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Please check entries for: • CRMCFSOLTP • CRMCREDCHE • CRMGENERAL • MKTPLBW • MKTPLSEM BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 6. 12. the entry for ECC has to be changed with the appropriate ECC5 logical system: 6. System: Procedure: CRM Program to update table CND_MAPM_CNV_REC SAP CRM Transaction code IMG path Program to update table CND_MAPM_CNV_REC Program has to be defined none After the client copy (only in case of client copy of course).13. The field SOURCE_ID is updated via transaction BDLS correctly with the ECC5 logical system.doc Page 97/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh. Result: inconsistencies.12.0 SAP CRM Transaction code IMG path Maintain Logical System for Action Box Transactions CRMC_CIC_AB_LSYS_ASS CRM Interaction Center WinClient Component Configuration Visible Components Action Box Settings Maintain Logical System for Action Box Transactions (just for ECC) In this customizing.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh • R3A_COMMON / CRM_DEFAULT_DESTINATION 6. But the field SOURCE_CLNT contains the client of the source system during the copy. Action: create et execute a report to update the field SOURCE_ID with the ECC5 client number. the table CND_MAPM_CNV_REC is incorrect. System: Procedure: CRM Maintain Logical System for Action Box Transactions CRM 4.12. dumps during the replication of pricing conditions. doc Page 98/ 125 .12.0 6. Use the following search criteria (could be adapted if too much b-docs). BRIDGE_CRM_ECC_V2_Consistent System Refresh.14. and delete them if yes. this tasks should be validated by functional team). Connect target system. Execute. Cleaning incorrect B-Doc. Launch transaction SMW01 (to be done in all client of target).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Check in the system if some rejected b-Doc remains (for pre-production system. CRM components reconnexion.0 The B-Doc should now have the status “processed”. Select and delete REPOSITORY related to SOURCE SYSTEM. Launch se38 and execute program: RSCMSPWS BRIDGE_CRM_ECC_V2_Consistent System Refresh.1. Use transaction strust to replace the source system certificate Launch transaction OAC0. Use Screenshot taken before the refresh to recreate the repository Z_<CS SID>_TES.doc Page 99/ 125 . 7. 7. CRM 4.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Select the line to be deleted (if validated) and use the delete button. Re-import Content Sever Repository informations. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. fill-in user: SAPCS and password: BRIDG012 and execute Should be succesfull Launch transaction CSADMIN and do the following (activate the certificate in tab “certificate” And Update Settings of the repository on TAB settings (use screen shot to do it).0 In Upper case.doc Page 100/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh. Checking Connection with Content server. BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 101/ 125 .0 Fill in settings Activate the certificate. Run the test and make sure that all the traffic lights are switched to green. enter the name of the test repository just created. Use SA38 or SE38 and program: RSCMST.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Execute. CRM 4.0 Choose number of test runs. Check the result (should be green). 7.2. Re-create IPC configuration. Checking IPC release. IPC has to be at the same patch level than CRM ABAP. Use transaction TTE_SIMULATION to check IPC release: Check the following. BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 102/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 Checking CRM BBPCRM Software component release. BBPCRM SC’s should be at the same release and patch than IPC server / dispatcher (Here 4.0 SP12). BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 103/ 125 BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 Check and change if necessary in the followings tables (use screenshots taken before to be sure). Use SE16 for tables: COMM_IPC_DEST; COMM_IPC_URL. COMM_IPC_DEST (should contain the connected IPC infos). COMM_IPC_URL (Check for target hostname). Checking IPC RFC Destinations. Destination name should contain the target IPC SID, check for target hostname and gateway hostname too). BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 104/ 125 CRM 4. BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 IPC Server.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh IPC Dispatcher.doc Page 105/ 125 . Launch SM59 to check the Trex destination.0 Make a Connection test (should be succesfull). BRIDGE_CRM_ECC_V2_Consistent System Refresh. but can different if V2 retrofii was not yet done). Checking / Changing TREX configuration. (Naming convention is TREX_<TREX SID>. Use screenshots taken before the refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh 7. Check the TREX is started and start-it if stopped.doc Page 106/ 125 . CRM 4.3. Check the following. Launch Transaction SRMO and check the followings. doc Page 107/ 125 . Launch SPRO transaction and check / change the following (use screenshot before the refresh).0 Make a connection test. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Check / Change the Catalog publication informations.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 108/ 125 . BRIDGE_CRM_ECC_V2_Consistent System Refresh.0 Launch SE38 (prog: COM_PCAT_IMS_FEED_INIT / variant: INI_YSEB2BCAT) to change the product catalog variant definition. use screen shot to recreate the right connection parameters if needed. Use SE16 for table CRMC_SAF_ APP_RFC BRIDGE_CRM_ECC_V2_Consistent System Refresh. Checking / Changing CRM-SAF Tool configuration.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 7. Check the followings.4.doc Page 109/ 125 . 0 7. Connect AIX server with root. Go to /sapmnt/<J2EE SID>/global/imsdocs Use: rm –r * Go to /sapmnt/<TREX SID>/global/index-master (or index) Use: rm –r * Replicate the new E-Selling Catalog to J2EE server.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Deleting old E-Selling Catalog Data (data from before the refresh). Launch transaction: COM_PCAT_IMS_FEED_INIT Fill-in the followings informations BRIDGE_CRM_ECC_V2_Consistent System Refresh. Make the E-Selling Catalog initial Replication.doc Page 110/ 125 .5. Restart the B2B web application (sometimes it’s better if possible to restart the complete J2EE server).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 111/ 125 .0 The RESULT SHOULD BE OK (GREEN LIGHT).do?umelogin=NO BRIDGE_CRM_ECC_V2_Consistent System Refresh. Check by connecting the B2B schneider application use the following links Use user = RUN<SID>EMP / password = bridg0 url: http://<hostname>:5<inst n° >00/b2b_secore/b2b/ init. 6. Configure the BMS on the CRM ABAP The messaging profiles are maintained by functional teams.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh The following web page (Schneider E-Sellin catalog). Send a mail to the functional team so they can change the parameters of the defined profiles: BSP URL => http://<hostname_of_ABAP_CRM>:80<Instance_number_ABAP_CRM>/sap/bc/bsp/sap/bsp_broadcast/cicbro ad.doc Page 112/ 125 . Means everything is OK.xml file located at /usr/sap/<SID>/JC<nn>/j2ee/cluster/server0/apps/sap.1. You can access this IMG activity directly by using transaction CRMC_CIC_BROAD.1 of the document). 7.doc to check the configuration. Refer to the documentation BRIDGE_CRM_SAP_BMS_Installation_Procedure. Change the port used for incoming sockets connections You will have to check the port used for incoming sockets connections (point 5. If the instance number of the target J2EE Engine is different to the source. you will have to change the web. Check the configuration of the Broadcast Messaging Server This application should be already deployed in the CRM J2EE Engine connected to the CRM ABAP.htm BRIDGE_CRM_ECC_V2_Consistent System Refresh.2.broadcast/servlet_jsp/BROADCAST/root/WEBINF The default port should be 1<JAVA_CRM_Instance_number>00 7.com/com.sap.6.0 7.6. CRM 4. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Applet Host Port number CRM 4. pressing key F6).g. Final tasks. 8. This will (re-)connect ECC and CRM systems to the central user administration. Make sure the logical system names of the target clients are included in the list. Check that transmission to your target clients was successful in the log displayed after completion.0 => http://<hostname_of_J2EE_server>:5<Instance_Number_J2EE_CRM>00/BROADCAST => the port you specified in the web. Connecting Systems to Central User Administration [for every client] Login the central user administration system with an administrative user and execute transaction code SCUA.xml of the deployed application (see above) 8. BRIDGE_CRM_ECC_V2_Consistent System Refresh.1. Switch to change mode (e. and save the settings.doc Page 113/ 125 . The operation might take some time. press the button Distribute to All Child Systems.doc Page 114/ 125 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. click on its logical system name in the list and press the Users button. On the next screen. You will see the remark “New System: Not All Users Were Copied” next to the newly copied target clients.0 To distribute the company addresses to all the systems not being synchronized call transaction code SCUG and press the button Company Addresses. To copy users from a target client to the central user administration system. BRIDGE_CRM_ECC_V2_Consistent System Refresh. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. To filter for user clone IDocs coming from the central user administration system. Important: By doing so you overwrite user data in the central system! You may want to correct user data in the target clients first before transferring them. enter the logical system name of the central user administration system as partner system and USERCLONE as message type.0 On the next screen. BRIDGE_CRM_ECC_V2_Consistent System Refresh. and Different Users and use button Transfer users to transfer them to the central user administration system. Identical Users. Enter the logical system name of the central user administration system (as Receiving System) and execute (e. using key F8).doc Page 115/ 125 .g. use transaction code SA38 to report SUSR_ZBV_GET_RECEIVER_PROFILES. select them and process them using the Process button. To trigger a text comparison of the roles created in the new child system. Finally logon the target clients (that is the newly copied ECC and CRM clients) and call transaction code BD87. choose all the users listed on the tabs New Users. If the are unprocessed ones. a background job should be scheduled to do this. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Use DB16 to launch a database check and search for warning and errors.doc Page 116/ 125 .0 As manual processing is not a solution generally.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Database check. Schedule it every 15 minutes. Let the job run as user ID CUA_ADM_BTCH. Create reasonable variants for these reports if the do not exist. 8.2. Create a background jobs called Z_RECEIVE_IDOC_CUA_<client number> using transaction code SM36 in the ECC and CRM target client containing the reports RSBTONEJOB and RBDAPP01. Search for warning or error.0 Launch DB14 to check for result (depending of the database sizedepending of database) Search for the last dbcheck log (FID = chk).BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. 8.3. Tablespaces free space check. Check the return code. identify the problem and solve it. and dbl click on the line. Use DB02 to check the tablespace freespace and at os level the sapdata file system freespace (reported by the DB check (DB16)) and datafiles distribution BRIDGE_CRM_ECC_V2_Consistent System Refresh.doc Page 117/ 125 . and use the “detail log button” if RC is different from 0. 8. CRM 4.0 Use the refresh button to update database size statistics.doc Page 118/ 125 . Search for tablespaces wich have more than 90% filled (depending of the tablespace size). Checking the system settings and client attributes. Use the “current size” button.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Check also that the tablespaces are in Autoextend OFF. All tablespace should the autoextend option to off.4. Use SE06 to check and / or modify the system settings (should be not modifiable). BRIDGE_CRM_ECC_V2_Consistent System Refresh. q1badm q14serv:q1badm 1> stopsap … Instance on host q14serv stopped … Q1B database stopped /usr/sap/Q1B/SYS/exe/run/stopj2eedb completed successfully q14serv:q1badm 2> exit q14serv:q1badm 3> logout q14serv:/usr/sap/trans_Q1B/bdwlixaa # su . Leave <sid>adm. ORA-01109: database not open … Database dismounted.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Logon the server with <sid>adm Launch stopsap command to stop sap instance.0.oraq1b q14serv:oraq1b 1> sqlplus '/ as sysdba'.2.64bit Production With the Partitioning and Data Mining options BRIDGE_CRM_ECC_V2_Consistent System Refresh. Database altered.2.2. SQL> startup mount. Stop you database again. Oracle. SQL*Plus: Release 10.0. Launch sqlplus. q14serv:/usr/sap/trans_Q1B/bdwlixaa # su . Log on with ora<sid> user.2. SQL> alter database archivelog.0 .0 .doc Page 119/ 125 . … Database mounted.5. Re-activate Oracle archive log mode. Start your database in mount mode Switch archive log to on. 2005. SQL>exit Disconnected from Oracle Database 10g Enterprise Edition Release 10.0 Use scc4 to check / modify the clients settings (for all client) check in screen copy made in step 0. SQL> shutdown immediate. All Rights Reserved. 8. Log on and launch a database check again. ORACLE instance shut down.Production on Fri Nov 23 14:05:31 2007 Copyright (c) 1982. Connected to an idle instance. Leave ora<sid> user Log-on with <sid>adm Re-start SAP system (and Oracle). Leave SQL and ora<sid> user. ….BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh q14serv:oraq1b 2> exit q14serv:oraq1b 3> logout q14serv:/usr/sap/trans_Q1B/bdwlixaa # su .0 Don’t forget to check if the ccms agent is well started. Re-importing Delta of Transport request.) Activate archive log mode: “alter database archive log.” Stop the database again (“shutdown immediate. Log-on with <sid>adm user.q1badm q14serv:q1badm 1> startsap …. Leave <sid>adm. 8. Log-on with <sid>adm user. You can check in the transport log system of the source system (STMS) which transport have been imported. Checking / enabeling archivelog mode. Database log mode Archive Mode Means that archive log is set to on. SQL> archive log list. Startsap the sap system.6. Log on with ora<sid> user. Instance on host q14serv started IGS on host q14serv started Starting CCMS Agent sapccmsr ---------------------------CCMS Agent sapccmsr already running CRM 4. BRIDGE_CRM_ECC_V2_Consistent System Refresh. Launch sqlplus (‘sqlplus ‘/ as sysdba’. transport have been imported into production environnement. You have now to switch your database to archive log mode to on. to have a consistent system those transport have to imported in the preproduction system. Since the target system was stopped for refresh.orazc0 zc2serv:orazc0 1> sqlplus '/ as sysdba'.”). Leave <sid>adm Use the following to check the actual archive log mode: zc2serv:/>su .doc Page 120/ 125 . Stop the sap system (“stopsap”). Ask the CCTeam for listing all transport imported from the beginning of the refresh and import them in the pre-prod system.7. Archive destination /oracle/ZC0/oraarch/ZC0arch Oldest online log sequence 2777 Next log sequence to archive 2782 Current log sequence 2782 8. Automatic archival Enabled Means that archive log is set to on. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4. Use transaction SU10 to unlock them. 8.4. Search for critical dump. Launch SM02 search and delete message relating to source system.0 The CCTeam is responsible for doing transport.doc Page 121/ 125 .10.10. Check and / or delete remaining SM02 messages. Check in section 5.8 Manual steps: Launch se61.11. so don’t do it yourself top avoid importing non requested transport orders. 8. Searching for critical warning or error. Restoring Login screen info. 8.8. Use ST22 to search for dump generated AFTER the refresh. 8. 8. Use SM21 to search for critical warning or error messages. Unlocking Project Users.13.9. BRIDGE_CRM_ECC_V2_Consistent System Refresh.12. and ask the CCTeam to be sure witch user have to be unlocked. Choose data element ZLOGIN_SCREEN_INFO Choose change. update with information taken in step 2. Re-schedule SAP Background Jobs.4. You can update data manually or re-import transport request created in step: 2.8 8. Ask the Controlm or Tools team to reschedule the standard jobs. der File” Download the certificate from the ESS J2EE instance / and For CRM J2EE Instances. CRM 4. Go to System Administration -> System Configuration -> Keystore Administration Click on “Download verify. we have to re-import the certificates of the Portal in ESS and CRM Web AS JAVA instances. Download the certificate of the portal.doc Page 122/ 125 . and uncompress it.0 8. Re-import certificates for SSO between Portal / ESS and Portal CRM (j2ee).14. All jobs should be finished successfully.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Wait for the first execution of each job. to be able to use this instance with ESS and CRM scenario. Take care specialy to all Middleware jobs for CRM (job name should start by MW*). select the certificate and export it to a file. Connect to this instance with Visual Administrator: Then Go to Services -> Keystorage. BRIDGE_CRM_ECC_V2_Consistent System Refresh. After the refresh. start transaction strustsso2: Remove the old entries in the system PSE tab by selecting the lines and clicking . BRIDGE_CRM_ECC_V2_Consistent System Refresh.BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.doc Page 123/ 125 .0 On the ECC and CRM instance. 0 Click on Click on Enter the <SID> of the system and the client (000 if it is a J2EE system) Repeat the operation for the other system Save the modification in the transaction screen. into the ECC system. Now.doc Page 124/ 125 .BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh Then import the certificates you have downloaded before. It appears in the Certificate part of the screen: CRM 4. Click the button and specify the path to the certificate. you the ESS connection should work again: BRIDGE_CRM_ECC_V2_Consistent System Refresh. BRIDGE TECHNICAL PROCEDURE CRM and ECC Consistent System Refresh CRM 4.0 8.doc Page 125/ 125 .15. BRIDGE_CRM_ECC_V2_Consistent System Refresh. A TECHNICAL VALIDATION of the component (CRM and ECC) should be done after each system refresh to be sure that nothing was forgotten. IF all is checked and OK. Final Check. make a global system check. END OF DOCUMENT. Before deliver your refreshed instance to the project. Take care of all exported stuff in step 0 and check if nothing was forgotten. you can deliver the system to the project team.
Copyright © 2024 DOKUMEN.SITE Inc.