Skip to main content

Cluster control migration from one server to another Server

 

Cluster control migration from one server to another Server

There are two ways to migrate Cluster Control from one server to another.

1.      Install Cluster Control on new server and add all the servers
2.      Install Cluster Control on new server and migrate the old monitoring data to new server

1.     Install Cluster Control on new server and add all the servers

This is the simplest method of migration when there are only few servers and historical data is not required. Manual steps are not required and easy to migrate.

The following steps are involved in this method.

1.       Install ClusterControl on the new server by using install-cc.sh script

2.       Setup passwordless SSH by copying the SSH key to all nodes

3.       Add all the nodes from Cluster Control GUI

2.     Install Cluster Control on new server and migrate the old monitoring data to new server

This is the recommended way to migrate when historical data is needed on new server.

 

The steps include:

 

1.       Install ClusterControl on the new server by using install-cc.sh script

2.       Export the cmon and dcps databases using mysqldump

3.       Copy the old CMON configuration files: /etc/cmon.cnf and /etc/cmon.d/* (if any)

4.       Replace any occurrences of old IP address in the new server

5.       Restore the cmon and dcps databases

6.       Transfer CMONAPI token value

7.       Setup passwordless SSH by copying the SSH key to all nodes

Comments

Post a Comment

Popular posts from this blog

Script to Collect Data Guard Physical Standby Diagnostic Information

Script to Collect Data Guard Physical Standby Diagnostic Information [ID 241438.1] -------------------------------------------------------------------------------- Modified 20-APR-2011 Type SCRIPT Status PUBLISHED Overview -------- This script is intended to provide an easy method to provide information necessary to troubleshoot Data Guard issues. Script Notes ------------- This script is intended to be run via sqlplus as the SYS or Internal user. Script ------- - - - - - - - - - - - - - - - - Script begins here - - - - - - - - - - - - - - - - -- NAME: DG_phy_stby_diag.sql -- ------------------------------------------------------------------------ -- AUTHOR: -- Michael Smith - Oracle Support Services - DataServer Group -- Copyright 2002, Oracle Corporation -- ------------------------------------------------------------------------ -- PURPOSE: -- This script is to be used to assist in collection information to help -
1 comment
Read more

ORA-01501: CREATE DATABASE failed

Problem: ======== During the creation of a new database the CREATE DATABASE command fails with the following errors: ORA-01501: CREATE DATABASE failed ORA-01519: error while processing file '?/rdbms/admin/sql.bsq' near line 406 ORA-00604: error occurred at recursive SQL level 1 ORA-04031: unable to allocate 2192 bytes of shared memory ("shared pool", "unknown object","KQLS heap","KQLS MEM BLOCK") Solution: ========= 1. Increase the shared_pool_size parameter in the init .ora file. 2. Shutdown abort your database. 3. Startup nomount your database. 4. Execute the CREATE DATABASE command again. Explanation: ============ If your shared_pool_size is too small, the CREATE DATABASE command cannot finish successfully. This happens typically on small test instances when you just want to test anything on an empty instance and do not want to waste too much memory on a server. In this case you often edit in
Post a Comment
Read more