Hi folks,
Currently we have a 3 tier HANA landscape and 3 tier SAP source system; development, staging, production with each Hana system replicating data from it's respective source system. We are about to do a system copy of SAP Production to SAP Staging so that our data volume on staging in both HANA and SAP closely simulates our production environment. When we do the system copy we will have to wipe out the destination schema in HANA staging and reload all the source system tables from SAP staging into Hana staging. If this reload takes an entire week then we will lose this environment for end user testing for that duration. In the end we want the schema to have the same exact name as it does before the system copy and reload. We do not want to create a new schema with a different name than the original and use schema mapping. So my question is there any way to do this and make it as seamless as possible so that there is no downtime and loss of testing environment? ie: maybe some way to replicate the new data into a new schema and then once completely loaded delete the original schema and then RENAME the new schema to the original name? Is that possible and can we change the mass transfer ID description?
Something like this;
Original Schema
ABC
Mass transfer ID 001, description 'ABC'
1) Reload new schema called XYZ mass transfer ID 002, description 'XYZ'. During this loading period of many days keep views pointing to original schema ABC.
2) Once XYZ fully loaded, delete schema ABC
3) Rename XYZ schema to ABC inside studio. Mass transfer ID 002 remains 002 but can we change description from 'XYZ' to 'ABC'.
PS: You may ask why not have different schema name and handle via schema mapping and it's because we found several advantages to having the same physical schema name throughout the landscape.
Thanks,
-Patrick