If you are getting the following:

2019-03-21 01:04:17,021 FATAL main:org.hsqldb.cmdline.SqlFile: SQL Error at 'UTF-8' line 6:
"alter table SETTINGS
    add column LDAP_USER_SEARCH_BASE varchar(1024),
    add column LDAP_USER_SEARCH_FILTER varchar(1024),
    add column LDAP_GROUP_SEARCH_BASE varchar(1024),
    add column LDAP_GROUP_SEARCH_FILTER varchar(1024)"
Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs
2019-03-21 01:04:17,021 FATAL main:org.hsqldb.cmdline.SqlFile: RollingbackSQL transaction.
2019-03-21 01:04:17,023 ERROR main:com.cloudera.enterprise.dbutil.SqlFileRunner: Exception whileexecutingddl scripts.
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

it's probably because you're running these SQL commands to setup the Cloudera database:

CREATE DATABASE scm DEFAULT CHARACTER SET utf8mb4 DEFAULT COLLATE utf8mb4_unicode_ci;
GRANT ALL ON scm.* TO 'scm'@'%' IDENTIFIED BY 'scm';

Or these:

CREATE DATABASE scm DEFAULT CHARACTER SET utf8mb4 DEFAULT COLLATE utf8mb4_general_ci;
GRANT ALL ON scm.* TO 'scm'@'%' IDENTIFIED BY 'scm';

Instead of something like this:

create database scm DEFAULT CHARACTER SET utf8;
grant all privileges on scm.* to 'scm'@'%' identified by 'scm';

Appears unicode or general, can throw an error with the cloudera–scm-server on install.

Thx,
TK