Cloudera Docs

Database and data cleanup

Use these H2 defaults and cleanup ordering when purging migration metadata or replication policies.

The embedded defaults apply unless you have configured external JDBC backends. For more information, see CMA database backends. For Cloudera Replication Manager integration context, see Cloudera Replication Manager Integration.

Table 1. Embedded H2 database default credentials
Role Database path Default credentials
CMA Master Server /var/lib/cma/data/db/cma-server admin / s3cret
CMA Auth Server /var/lib/cma/data/db/cma-auth root / root
CMA Agent Server /var/lib/cma-agent/data/db/cma-agent admin / s3cret
  1. List Cloudera Replication Manager replication policies on the target cluster using the Cloudera Manager API. 
    curl -s -u admin:admin \
  "http://<target-cm-host>:7180/api/v49/clusters/Cluster%201/services/HDFS-1/replications"
  2. Delete each policy through the Cloudera Manager API. 
    curl -s -X DELETE -u admin:admin \
  "http://<target-cm-host>:7180/api/v49/clusters/Cluster%201/services/HDFS-1/replications/<id>"
  3. Clean the H2 database on the CMA Master host.

    Disable referential integrity temporarily when untangling foreign-key chains.

  4. Restart CMA Master.

    The CMA Master repopulates essential plugin data from YAML configuration files at startup.