In our case HANA dev tenant (HANA_D)is connected to one EXADATA instance(EXA_D) and HANA SIT (HANA_S)is connected to another EXADATA(EXA_S) instance via oracle ODBC adapter.
also EXA_D and EXA_S has different schema inside it
Problem is when i deploy the virtual tables from HANA_D to HANA_S, how can i make sure that after deployment of virtualtables HANA_S is pointing to EXA_S and with specific schema.
in the picture attached the blue marked property of the virtual table will remain constant during deployment but the black marked will change as in SIT the remote name and schema are different
Better to undertand our use case is below:
scenario(HANA_D->EXA_D->Schema_1) has to be deployed to HANA_S->EXA_S->Schema_2.
Its really urgent and important for our team to know this concept.
We tried all means my exploiting cups but no help?
can i handle this kind of exception in GIT??