Hi All,
What are the exact steps to clone a DB in cloud/remote installation?
(Ex: From PROD to MIG)
Best answer by CRUNDELL
View original
IFS Cloud Clone
Userlevel 6
+13
Userlevel 7
+22
Hi
you have to create an IFS case to do this because you aren’t able.
So in IFS Cloud if we want to copy our LIVE/PROD environment to our TEST use-place environment we can not do so - and have to get IFS to do this?
This doesn’t seem right - how can we have a realistic TEST environment? Is it only IFS that can do this - or could a Partner.
To confirm, are you cloning cloud to cloud? Or cloud to on prem? Cloud to cloud is a ticket and it is very easy. Takes them about 4-5 days to complete. Cloud to on prem...that is much, much more difficult. I can explain what we went through but as far as I’ve been advised, there is no official procedure.
Userlevel 7
+22
So in IFS Cloud if we want to copy our LIVE/PROD environment to our TEST use-place environment we can not do so - and have to get IFS to do this?
This doesn’t seem right - how can we have a realistic TEST environment? Is it only IFS that can do this - or could a Partner.
All our environments are in cloud. If we want to create a copy we have to create an IFS case. This is the process I know. Maybe they have other process but I don’t think so.
Hi,
We have our environment IFS Cloud on prem. Do you have any idea about the procedure on prem to on prem?
Thanks,
Userlevel 7
+22
Hi,
We have our environment IFS Cloud on prem. Do you have any idea about the procedure on prem to on prem?
Thanks,
Hi
If it is on prem then you have do it by yourself. Because IFS doesn’t access to your (local) server and make the copy.
For prem to prem - you should be able to do this in house with a good DBA and an IFS admin per your normal cloning / refreshing procedures.
For cloud to on prem refresh you’ll need to:
- Define a pathway to receive large file transmissions from the cloud to your on prem environment - this was particularly challenging for us and the cloud team is incredibly unhelpful here. The FTPS (or SFTP) pathways defined in your COG do not seem to support the transmission from IFS to customer...only customer to IFS.
- Request a backup of the source environment via a ticket for the cloud team. I would request this with the assistance of a good DBA as the source database will likely need to be split up in a way that your DBA can put back together. We struggled here as well as instructions that made sense for us were not documented as part of cloud procedures so the cloud team wouldn’t do the split in a way that we could put back together.
- Perform some application and middleware configuration after the refresh
FYI, there are a series of tables that you will not want to clone between your PROD and non-PROD environments in order to keep your non-PRODs from connecting with third-party production systems (“Refresh Exclusion Tables”). Below is a list of the these for Cloud 21R2 that I got from IFS. We have used this through several refreshes already. Procedurally, you have to export these before you clone the DB and then import them back after the clone. Re-Quest, our DBA services provider handles all of this for our on-premise install of Cloud. They have also automated this process for our Apps 9 install and are working on this for Cloud.
Refresh Exclusion Tables
- brbase_property_tab
- common_messages_tab
- config_instance_param_tab
- config_instance_tab
- connect_envelope_tab
- connect_print_agent_task_tab
- connect_queue_tab
- connect_reader_tab
- connect_sender_tab
- connect_server_tab
- connect_simple_routing_tab
- connect_transformer_tab
- custom_connector_library_tab
- custom_reader_param_tab
- custom_sender_param_tab
- edm_location_tab
- edm_location_user_tab
- fnd_monitor_category_tab
- fnd_monitor_entry_tab
- fnd_setting_tab
- media_archive_tab
- plsqlap_environment_tab
- remote_assist_group_user_tab
- remote_assistance_customer_tab
- remote_assistance_group_tab
- remote_assistance_user_ab
- report_plugin_settings_tab
- routing_address_tab
- routing_rule_address_tab
- routing_rule_condition_tab
- routing_rule_tab
- scheduling_config_tab
- svcsch_configuration_tab
- tm_serve_parameters_tab
Refresh Exclusion Tables for Security
Excluding these additional tables will leave your security ‘as is’ in your cloned environment instead of overwriting it from the source.
- fnd_bpa_grant_tab
- fnd_grant_role_tab
- fnd_proj_action_grant_tab
- fnd_proj_ent_action_grant_tab
- fnd_proj_entity_grant_tab
- fnd_projection_grant_tab
- fnd_role_tab
- fnd_user_role_tab
- ifsiamsys
- pres_object_grant_tab
- system_privilege_grant_tab
Userlevel 2
+6
Hi Darshana,
If you have a IFS Cloud services contract, i.e. everything fully managed by IFS (so, not on premise), you do not have any access to the Oracle database in the Use Place at it is in their private cloud.
If you want for instance PRD envt to be cloned to UAT, at the moment you have to open a “classical” case for that in the customer portal.
Be careful because the time slots IFS provides for those kind of jobs are limited and you have to book your cloning activity I would say at least 2 weeks in advance. I regularly struggle with them to respect the schedule I need.
A dedicated page to ask for that kind of job should be available soon in the Cloud Services tab of the customer portal.
One more schema!
FYI, we have found that it works best to ALWAYS export IFSIAMSYS before cloning and import this back afterwards. In other words, would suggest treating the IFSIAMSYS schema as a “refresh exclusion table” and not as a “refresh exclusion table for security” (above).
Here are a few more tables that I would add to the Refresh Exclusion List
Refresh Exclusion Tables Additions...
- ifsiamsys schema - this is mentioned above, needed to retail Azure SSO/environment.
- routing_address_runtime_tab
- fnd_branding_tab - this and the next 4 tables including brading, banners, etc. We separated these by environment with separate labels at top so users can tell which one they are in.
- fnd_branding_property_tab
- fnd_branding_resource_tab
- fnd_branding_token_tab
What about systems using a PSO Workbench connection? Where are the PSO connection details located in the database?
Userlevel 3
+7
What about systems using a PSO Workbench connection? Where are the PSO connection details located in the database?
It’s stored in 32. scheduling_config_tab above.
Specific settings for the Scheduling Configuration used by Service Management are stored in 33. svcsch_configuration_tab above.
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.