Hi @kvinod ,
Here is the snippet from the article:
For CM 5.13.x and below, use the following process to remove the license manually from the database.
1. Log in to Cloudera Manager and stop the Cloudera Management Services. (Host Monitor, Event server, Alert Publisher, etc)
2. From the Cloudera Manager server shell, Stop Cloudera Manager.
service cloudera-scm-server stop
3. Confirm the Cloudera Managerdatabase instance name and credentials.
grep com.cloudera.cmf.db /etc/cloudera-scm-server/db.properties
com.cloudera.cmf.db.type=$DBTYPE
com.cloudera.cmf.db.host=$DBHOST:$DBPORT
com.cloudera.cmf.db.name=$DBNAME
com.cloudera.cmf.db.user=$DBUSER
com.cloudera.cmf.db.password=$DBPASS
For the remainder of this process the $DB variables will be used, please replace with your configured values. This document will cover $DBTYPE of Postgres or MySQL. $DBPORT may not exist in the properties file if using the default port.
4.Backup the database instance.
IMPORTANT: Ensure to create the database backup for this step.
For MySQL:
# mysqldump -h $DBHOST -P $DBPORT -u $DBUSER -p $DBNAME > /root/cmbak.`date +%Y-%m-%d:%H:%M`.sql
For Postgres:
# pg_dump -h $DBHOST -p $DBPORT -U $DBUSER -W $DBNAME > /root/cmbak.`date +%Y-%m-%d:%H:%M`.sql
5. Log in to the database
For MySQL:
# mysql -h $DBHOST -P $DBPORT -u $DBUSER -p $DBNAME
For Postgres:
# psql -h $DBHOST -p $DBPORT -U $DBUSER -W $DBNAME
Type the $DBPASS when requested.
6. Update the record to remove the license key.
update CONFIGS set VALUE = '' where ATTR = 'license_key';
7. Confirm the license key is removed.
select CONFIG_ID, ATTR, VALUE from CONFIGS where ATTR = 'license_key';
+-----------+-------------+-------+
| CONFIG_ID | ATTR | VALUE |
+-----------+-------------+-------+
| 79 | license_key | |
+-----------+-------------+-------+
1 row in set (0.00 sec)
8. Quit database:
For MySQL:
mysql> quit
For Postgres:
scm> \q
9. Start Cloudera Manager from the server shell:
service cloudera-scm-server start
10. Login to Cloudera Manager and start the Cloudera Management Services. (Host Monitor, Event server, Alert Publisher, etc)
11. Restart the cluster services to confirm everything is okay.
Thanks and hope this helps,
Li
