We have restored hfm schema from one env to other env in 188.8.131.52
while validating hfm app from workspace getting communication error
so we tried to connect to hfm client using the cluster , we are not able to connect to hfm app
then we tried to connect to hfm app using individual server ..we are able to connect to hfm app using indivdual server from client then we confirmed that this is an issue with the hfm cluster
and we checked the cluster info in the restored db and we found that it is showing the source cluster.....as per oracle advice we have configured the hfm db and registered app/cluster .....the issue seems to be fixed but i need a confirmation whether this is the right approach we need to follow every time we migrate hfm schema from one env to other env or its just a work around..
can you advice what is the exact procedure to migrate hfm schema from one env to other env.
Hi, That's the process to be followed if you are copying the schemas from one environment to the other. Copying the back end database doesn't change the information in the tables. You have to run the configuration again and register it with correct servers. Even the applications have to be registered again.
Anyways Oracle doesn't recommend the above approach. There are specific tools which are shipped with the product which server the purpose. You can use the copyapp utility to copy the applications from one environment to the other. You then can use the schema upgrade utility to upgrade the applicaions if copying from one version of HFM to the other. Finally register the applications with SS in the target environment. This approach doesn't require any DBA support. You should be able to do it all by yourself. But in your earlier approach you need DBA help to copy the schemas. Unless and until you run into any issues you are not supposed to try copying the schemas.
Hope this helps!