My tryst with an MCOD DB refresh
In this blog, I would like to write about the QA refresh of an MCOD database that I did recently.
Our QA landscape has ECC, Portal and PI installed in separate servers but have only one database server for all those instances using the same database in MCOD. MCOD allows installation of several components independently in one single database (in our case, ECC, Portal and PI). An MCOD has one database and different schemas. More details about MCOD can be found Multiple Components in One Database (MCOD).
The Requirement: Refresh the QA ECC using the production backup from tape. This was to check if the backup in tape could be used in case of a disaster.
The dilemma: A database copy from production to QA, will also copy the production schemas. This will replace all the systems (including Portal and PI). A system copy using R3load was out of question, since the DR strategy had to be tested.
1. Run sapinst to create an export of the QA Portal (System copy AS Java) and QA PI (System copy AS ABAP + Java). Please refer to the system copy guide for more details. Keep a safe copy of this export.
2. Uninstall QA Portal and PI.
3. Perform the DB copy. I will be explaining this step in detail in my next blog.
4. Re-Install Portal and PI using the export created in step 1.
These additional steps were needed because of an MCOD database. Refreshing a single instance on a single database instance is much easier, and less time consuming. Even though MCOD systems provide some amount of flexibility and scalability, administratively they are challenging. Especially in the case of backup and restore. I feel a better approach would be to have separate Oracle installations for each SAP component. This way future DB refreshes can avoid those additional (error-prone) R3load steps. But that will be a whole new project in itself.
Looking forward to the comments and opinions from other members.