Syntax for scm_prepare_database.sh
Review the syntax of the scm_prepare_database.sh script before you run
it to configure the Cloudera Manager database.
The syntax for the scm_prepare_database.sh script is as follows:
sudo /opt/cloudera/cm/schema/scm_prepare_database.sh [options] <databaseType> <databaseName> <databaseUser> <password>To create a new database, you must specify the -u and -p
parameters for a user with privileges to create databases. If you have already created the
database as instructed in Step 4: Install and Configure Databases, do not specify
these options.
The following tables describe the parameters and options for the
scm_prepare_database.sh script:
| Parameter (Required in bold) | Description |
|---|---|
<databaseType> |
One of the supported database types:
|
<databaseName> |
The name of the Cloudera Manager Server database to use. For PostgreSQL
databases, the script can create the specified database if you specify the
-u and -p options with the credentials of a user
that has privileges to create databases and grant privileges. The default database
name provided in the Cloudera Manager configuration settings is scm,
but you are not required to use it. |
<databaseUser> |
The username for the Cloudera Manager Server database to create or use. The
default username provided in the Cloudera Manager configuration settings is
scm, but you are not required to use it. |
<password> |
The password for the <databaseUser> to
create or use. If you do not want the password visible on the screen or stored in the
command history, do not specify the password, and you are prompted to enter it as
follows: |
| Option | Description |
|---|---|
-?|--help |
Display help. |
--config-path |
The path to the Cloudera Manager Server configuration files. The default is
/etc/cloudera-scm-server. |
-f|--force |
If specified, the script does not stop if an error occurs. |
-h|--host |
The IP address or hostname of the host where the database is installed. The
default is to use localhost. |
-p|--password |
The admin password for the database application. Use with the -u
option. The default is no password. Do not put a space between -p and
the password (for example, -phunter2). If you do not want the
password visible on the screen or stored in the command history, use the
-p option without specifying a password, and you are prompted to
enter it as
follows: |
-P|--port |
The port number to use to connect to the database. The default port is:
|
--scm-host |
The hostname where the Cloudera Manager Server is installed. If the Cloudera
Manager Server and the database are installed on the same host, do not use this option
or the -h option. |
--scm-password-script |
A script to execute whose stdout provides the password for user
SCM (for the database). |
-u|--user |
The admin username for the database application. Use with the -p
option. Do not put a space between -u and the username (for example,
-uroot). If this option is supplied, the script creates a user and
database for the Cloudera Manager Server. If you have already created the database, do
not use this option. |
The following examples demonstrate the syntax and output of the scm_prepare_database.sh script for different scenarios:
Example 1: Running the script when MySQL or MariaDB is co-located with the Cloudera Manager Server
This example assumes that you have already created the Cloudera Management Server database and database user, naming both scm:
sudo /opt/cloudera/cm/schema/scm_prepare_database.sh mysql scm scmEnter SCM password:
JAVA_HOME=/usr/java/jdk1.8.0_141-cloudera
Verifying that we can write to /etc/cloudera-scm-server
Creating SCM configuration file in /etc/cloudera-scm-server
Executing: /usr/java/jdk1.8.0_141-cloudera/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/java/postgresql-connector-java.jar:/opt/cloudera/cm/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.
[ main] DbCommandExecutor INFO Successfully connected to database.
All done, your SCM database is configured correctly!Example 2: Running the script when MySQL or MariaDB is installed on another host
This example demonstrates how to run the script on the Cloudera Manager Server host (cm01.example.com) and connect to a remote MySQL or MariaDB host (db01.example.com):
sudo /opt/cloudera/cm/schema/scm_prepare_database.sh mysql -h db01.example.com --scm-host cm01.example.com scm scmEnter database password:
JAVA_HOME=/usr/java/jdk1.8.0_141-cloudera
Verifying that we can write to /etc/cloudera-scm-server
Creating SCM configuration file in /etc/cloudera-scm-server
Executing: /usr/java/jdk1.8.0_141-cloudera/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/java/postgresql-connector-java.jar:/opt/cloudera/cm/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.
[ main] DbCommandExecutor INFO Successfully connected to database.
All done, your SCM database is configured correctly!Example 3: Running the script to configure Oracle
sudo /opt/cloudera/cm/schema/scm_prepare_database.sh -h cm-oracle.example.com oracle orcl sample_user sample_passJAVA_HOME=/usr/java/jdk1.8.0_141-cloudera
Verifying that we can write to /etc/cloudera-scm-server
Creating SCM configuration file in /etc/cloudera-scm-server
Executing: /usr/java/jdk1.8.0_141-cloudera/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/java/postgresql-connector-java.jar:/opt/cloudera/cm/schema/../lib/*cloudera.enterprise.dbutil.DbCommandExecutor /etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.
[ main] DbCommandExecutor INFO Successfully connected to database.
All done, your SCM database is configured correctly!