on 01-09-2013 9:34 AM
Hello
We are actually planning a hardware platform change from Unix Sun Solaris SPARC to IBM AIX.
We have several SAP systems to move. But the idea is to move only the DB to AIX platform and to install/keep SAP application server on Solaris side.
We use Oracle 11.2
We have :
1 Solution Manager 7.01 ( ABAP + Java in unicode )
6 ECC6 EHP4 systems ( ABAP non unicode )
2 Netweaver 7.0 BI systems ( ABAP non unicode )
2 Netweavers 2004s systems for the SAP Portal ( Java )
I would like to have advices concerning such migration. For me it's only Heterogeneous System Copy
What are the options ? What are the risks and what are the different steps ?
Thanks for your help.
Franck
Hi Franck,
Please find the Check List for SAP Database Migration. I followed this Document for migrating many SAP Databases from HP-UX to AIX. The process will be almost same for all Database migrations. Hope this checklist will help you in doing your task. Kindly feel free to contact me in case of any issues during Database Migration.
Task # | Task Description | Dependant Tasks |
1 | Request diskspace, UIDs | - |
2 | Create user ID as per request | 1 |
3 | Allocate diskspace, sudo, and other tasks associated with SAP DB migration as per request | 1 |
4 | Verify home directory is set correctly to /usr/sap/<SID>/<sid>adm on the middleware Server. May have to make <SID> and <sid>adm directories | 2 |
5 | Pre-Migration Tasks | 4 |
6 | Run the Export Preparation step on source database server | 5 |
7 | Shutdown SAP middleware instance | 6 |
8 | Run Database Instance Export step on source database server | 7 |
9 | Set permissions on chmod 777 /EXPORT_SAP/EXPORT/JAVA/TOOLS/SLTOOLS.SAR | 8 |
10 | Update /etc/oraInst.loc to path /oracle/<sid>//oraInventory on target server | 8 |
11 | Run Database Instance Import step on target database server | 9,10 |
12 | Revert /etc/oraInst.ora path back to inventory_loc=/u02/app/oracle/oraInventory | 11 |
13 | Create backup for profiles, security files and tnsnames.ora on Middleware and Database server | 11 |
14 | Copy the following files from the new DB server to Middleware server A. /usr/sap/<SID>/SYS/global/security/data/SecStore.key B. /usr/sap/<SID>/SYS/global/security/data/SecStore.properties C. /usr/sap/<SID>/SYS/profile/DEFAULT.PFL D. /usr/sap/<SID>/SYS/profile/oracle/tnsnames.ora | 11 |
15 | goto RZ10, select DEFAULT.PFL and update SAPDBHOST & j2ee/dbhost parameters to the new DB server | 14 |
16 | Update tnsnames.ora on middleware server and dbserver; /usr/sap/<SID>/SYS/profile/oracle | 11,14 |
17 | Update configtool settings | 11,14,15,16 |
18 | Post Migration Steps | 17 |
19 | Inform QA Team for Validation | 18 |
20 | Test all the applications | 19 |
21 | Decide on Go/No-go | 20 |
22 | Send out Completion mail to all stakeholders | 21 |
Task # | Task Description | Time |
1 | Copy profiles to HP db server from middleware server. Create folder in /usr/saptmp called <SID>_SYS first and copy all directories there first. Make sure groups, ownerships, softlinks are correct | 30 minutes |
2 | Correct profiles on HP DB server b/c DB is in /u02 vs. /oracle | 30 minutes |
3 | Check the database size on old server | 10 minutes |
4 | On new server, verify ID's, home directories, copy policy file, java, and profile directory. Verify /sapmnt exists and permissions/ownership is correct | 45 minutes |
5 | Set environment variables | 10 minutes |
6 | Prep for the database stats - make undefined & sapcheck directory, copy brtools, R3 tools, move .pse file | 30 minutes |
7 | Verify the init<SID>.sap exists | 10 minutes |
8 | Copy profiles from middleware server to target database server | 10 minutes |
9 | Verify rootpre.sh has been run on the target server | 10 minutes |
10 | Create /Oracle sub-directories on traget server | 15 minutes |
11 | Backup SAP Database | 45 minutes |
12 | Drop synonyms (if applicable) | 5 minutes |
13 | Lock users in SAP middleware application | 5 minutes |
14 | Remove Invalidated Objects (correct SAP table and Z custom tables before export via SE14) | 10 minutes |
15 | Make sure "undefined" directory didn't disappear from /tmp. If it did, re-copy from /usr/saptmp/<SID>_SYS | 10 minutes |
16 | Generate the migration Key from SapService Market place. | 30 minutes |
Run Database Instance Import step on target database server
Task # | Task Description | Time |
1 | Login to the required folder and start sapinst | 10 minutes |
2 | Fill the required paramter variables as required | 45 minutes |
3 | Verify the parameter values and update wherever necessary | 25 minutes |
4 | Enter the migration key generated from Service MarketPlace | 10 minutes |
5 | Monitor the process and resolve corresponding issues till phase 8 of the import | 2 hours |
6 | Install Oracle Database | 40 minutes |
7 | Apply Oracle Patch set and run corresponding scripts | 30 minutes |
8 | Resume the import process and continue monitoring | 12 hours |
Task # | Task Description | Time |
1 | Shut down SAP middleware | 20 Minutes |
2 | Update DNS on network | 2 hour |
3 | update listener, create user ids and indexes that were created directly in Oracle | 1 hour |
4 | Shutdown old SAP database | 10 Minutes |
5 | Start up middleware application | 15 Minutes |
6 | bounce SAP Application Server to get a clean restart and make sure Java stack starts | 30 Minutes |
7 | execute SGEN | 6 Hours |
8 | Verify Java stack | 30 Minutes |
9 | Re-create Synonyms dropped before migration | 15 Minutes |
10 | Execute the ABAP program SDB3FORA | 15 Minutes |
11 | Run stats on required tables (especially BSIS) | 2 Hours |
12 | Update SAP Service Marketplace with new DB configuration data | 30 minutes |
13 | Unlock users | 10 minutes |
No Go Decesion
1 | Shutdown middleware, then call out Database Team |
2 | Inform Database Team to revert DNS IP address configuration from new to old server |
3 | Shutdown database |
4 | Restore old database, |
5 | Move IP address back to HP server |
6 | Start up old database |
7 | Create a ticket for Disk Re-claim, DB backups |
Thanks and Regards,
Bhabani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.