MC/SG Move a package from a cluster to another

[VIGNOLA,ALESSANDRO]

Hello, customer'd like to move an oracle db clusterd with service guard to another cluster. Is it possible to do it? In this moment I suggested to create the new package on the second cluster and then migrate the db from the first one. thanks Alex

[Jozef_Novak · Accepted solution]

Hello,

this is pretty much possible. Create a new package in the other cluster and copy the configuration file and control script (SG version prior to 11.18) over from the original cluster. Migrate your shared volume group using export / import procedure. Make sure that your new cluster nodes are compatible with your Oracle version in terms of architecture, OS, patches and so on.

J.

[Steven E. Protter]

Shalom,

If you have cluster package configuration on one server, you can copy the configuration to a second node in the cluster.

The point of the documentation you quote is this: To have a package to move it is necessary to create one. Once its created, that control script can be copied to the second node.

You can take package control scripts from one cluster and copy them to a second cluster. You will need to modify certain aspects of the cluster control script to get it to work.

An example may help.

Cluster Tiger has an oracle package control script with a floating IP address of 192.168.0.10

The package control script can be copied to cluster Viper via scp,sftp or even ftp.

Before its going to work on cluster Viper, it needs a unique floating IP address.

If it hasn't been mangled, the cluster control script on Cluster Tiger has documentation. All you have to do is copy it across to the new cluster, make necessary modifications and away you go.

SEP

[VIGNOLA,ALESSANDRO]

ok. so I should:
- create the package structure on new cluster.
- trying the vgimport of the shared disks. check for oracle integration and network topics.
- close the original package
- cmdeleconf on the old package on original cluster
- cmcheckconf and cmapplycong of the package on the new cluster.
- test the switch

[Mel Burslan]

After closing (I think you meant halting with cmhaltpkg command) the original package, you do not have to remove it immediately. You export the vg(s) associated with this package and import them on the new cluster nodes. then cmcheckconf and then cmapplyconf if everything looks good.

After running the package on the new cluster for a few days and testing a failover scenario just in case, successfully, you can safely delete the package configuration from the original cluster. Keeping it there until everything is known working well on the new cluster, is a good measure, just in case something goes wrong.