Install and Configure Your Database Software

Before running the CA UIM installer, you must first install and prepare the database software for the CA UIM database. This article describes the steps required to configure each supported type of database software for CA UIM.
uim835
Before running the CA UIM installer, you must first install and prepare the database software for the CA UIM database. This article describes the steps required to configure each supported type of database software for CA UIM.
If you have questions regarding which database vendor software is supported with CA UIM, refer to the Compatibility Support Matrix. For general database installation procedures, refer to the product documentation provided by your database vendor.
Contents
Once you have determined with method you will use, you can follow the instructions in this article for your specific database software.
Determine Your Database Creation Method
Before continuing, determine the method that you will use to create the UIM database.
CA UIM Installer Creates the Database Schema and User
You can allow the CA UIM installer to create the UIM database. If you use this method, you must allow the installer to access a database account with administrator privileges. Examples include:
  • root in MySQL
  • sa in MS SQL Server
  • SYS in Oracle
When you run the installer, you will enter the credentials for designated account.
If you choose this installation method, skip the
Manual Creation of the Database Schema (or Tablespace) and User
section for your database software.
Manual Creation of the Database Schema and User
If you do not want to give the CA UIM installer access to an administrator account, you can create the UIM database and associated user manually. We recommend manual database creation in environments that have a dedicated database administrator. If you choose to create the database and user in advance, make sure to choose
Use existing database
when prompted by the CA UIM installer. Do not choose to create a new database.
General Requirements
We recommend that you begin with a fresh database installation on a clean system. Using a pre-existing database can cause subtle configuration conflicts that are hard to diagnose and make installation unnecessarily difficult.
Database Password Requirements
A UIM database password cannot contain the following ASCII characters:
  • %
  • /
  • @
Microsoft SQL Server
CA supports only the full licensed product version with database authentication or Windows authentication for production environments. 
To obtain a copy of Microsoft SQL Server go to www.microsoft.com/sqlserver/ (not affiliated with CA Technologies). Make sure the version is compatible with your hardware.
Follow the installation instructions available with the download. 
While both the Enterprise and Standard Editions of MS SQL Server will work with CA UIM, we generally recommend that you use the Enterprise edition.
Configuring Microsoft SQL Server
The simplest solution:
  • Accept the default instance name when you install Microsoft SQL Server
  • Use the default port (1433) when you install CA UIM
Other solutions have different requirements. If you:
  • Use a non-default instance name for the Microsoft SQL Server you must use the default port (1433) when installing CA UIM.
  • Use a port 
    other
    than 1433 for CA UIM, you 
    must
    use the default MS SQL Server instance name. 
During UIM server installation you select one of these authentication options:
  • SQL Server with SQL Server login
    : You must provide the SQL server user name and password during installation. No modifications are needed. 
  • SQL Server with Windows authentication
    : You might need to make database modifications in advance, as described in the next section.
Requirements for Windows NT Authentication
Windows authentication has these requirements:
The user installing CA UIM must have the same administrative rights as those used to install the SQL server, and supply those credentials during the installation. Specifically, the data_engine probe must have identical administrative rights on both the CA UIM system and the database system.
  • Run the installer as the domain logon user to be associated with the CA UIM Server installation.
  • After installation, you must:
    • The 'Nimsoft Robot Watcher' NT service Logon User will be the same as used during UIM Server installation. This service starts the robot and thus the new user needs to have full permissions to the UIM Server installation folder and logon privileges to the SQL Server.
    • CA cautions against changing the logon user value which could result in the robot either not being able to start or unable to function normally due to file permission issues. If a change is made, be sure the login user is specified in the <domain>\<nt_username> format so that the user has full permissions to the Nimsoft install directory contents.
CA UIM Installer Creates the Database Schema and User
If you want the CA UIM installer to create the SQL Server database, then you must allow the installer to access an account with administrator privileges. You will supply these user credentials when you run the CA UIM installation Wizard. 
Manual Creation of the Database Schema and User
Follow these steps:
  1. Log in to SQL Server Management Studio as the system administrator (sa).
  2. Execute the following commands individually:
    CREATE DATABASE <UIM_db_name>; USE <UIM_db_name>; CREATE LOGIN <UIM_db_user> with PASSWORD ='<UIM_db_password>', DEFAULT_DATABASE = <UIM_db_name>; CREATE USER <UIM_db_user> FOR LOGIN <UIM_db_user>; EXEC sp_addrolemember 'db_owner', <UIM_db_user>; EXEC sp_addmessage @msgnum = 55000, @severity = 16, @msgtext = N'%', @replace = 'replace', @lang = 'us_english';
MySQL Server
You can obtain a copy of the open-source MySQL database software from http://dev.mysql.com/downloads/. Make sure the version is supported and compatible with your hardware. You can use either the Community Server version or a licensed version. 
MySQL variables must be set as follows:
  • lower_case_table_names: 
  • local_infile:
    ON
While not typically required, we recommend that you also set the following variables:
  • log_bin:
    ON
    Binary logging is required if using replication or certain data recovery operations. Refer to your MySQL documentation for details.
  • log_bin_trust_function_creators:
    ON
     (if log_bin is set to
    ON
    )
  • binlog_format:
    mixed
    (if log_bin is set to
    ON
    )
To check your settings:
  1. Log in to the MySQL server as the administrator.
  2. For each variable, execute:
    show variables like 'variable_name';
  3. If a variable is incorrect or missing, edit the MySQL server configuration file as instructed in your MySQL documentation. 
  4. Restart the database after making changes. 
MySQL in Large Environments
If you are preparing for a large-scale or major deployment, you must set additional database parameters to allow for the greater demands of such an environment. CA recommends you begin with the values shown in the following example, and then fine-tune settings depending on your circumstances. 
As the MySQL administrator, add these lines to the MySQL server configuration file:
[mysqld] max_heap_table_size = 134217728 query_cache_limit = 4194304 query_cache_size = 268435456 sort_buffer_size = 25165824 join_buffer_size = 67108864 max_tmp_tables = 64
Manual Creation of the Database Schema and User
To manually create the database and user and grant the require privileges, follow these steps:
  1. Log in as the MySQL administrator.
  2. Create the database. Execute:
    CREATE DATABASE IF NOT EXISTS <uim_db_name> DEFAULT CHARACTER SET = utf8 DEFAULT COLLATE = utf8_unicode_ci;
    where <
    uim_db_name>
    is the desired database name.
  3. Create the user and assign required privileges. Execute:
    CREATE USER '<uim_db_owner>'@'%' IDENTIFIED BY '<uim_db_owner_password>'; GRANT ALL PRIVILEGES ON <uim_db_name>.* TO 'uim_db_owner'@'%'; FLUSH PRIVILEGES;
    where
    uim_db_owner
    is the desired user name for the owner,
    uim_db_owner_password
    is the desired password, and
    uim_db_name
    is the name of the database you created. 
    The single-quotation marks (') are required.
Oracle
Required Oracle Environment
The Oracle Instant Client must be installed on the CA UIM system so it can access the Oracle database. 
Follow these steps:
  1. Go to www.oracle.com and select 
    Downloads > Instant Client
    .
  2. Click the link for the operating system and hardware of your system.
  3. Download the zip file for the 
    Instant Client Package - Basic
    .
  4. Install the Instant Client according to the directions on the web site. The UIM installer will ask for the location of the Instant Client.
  5. Restart the system. 
Required Oracle Configuration
The Oracle administrator must set required configuration parameters before installing CA UIM.
Follow these steps:
  1. As the Oracle database administrator, execute:
    ALTER SYSTEM SET PROCESSES = 300 SCOPE=SPFILE; ALTER SYSTEM SET SESSIONS = 335 SCOPE=SPFILE; -- 1.1 * PROCESSES +5 ALTER SYSTEM SET OPEN_CURSORS=500 SCOPE=BOTH; ALTER SYSTEM SET NLS_COMP=LINGUISTIC SCOPE=SPFILE; ALTER SYSTEM SET NLS_SORT=BINARY_AI SCOPE=SPFILE;
  2. Restart the database.
Turn off the Oracle Recycle Bin
If you will install the Unified Management Portal (UMP), then the recycle bin must be turned off before you install UIM Server.
Follow these steps:
  1. Use a tool such as SQL Developer to connect to the Oracle database.
  2. Enter the following commands:
    ALTER SYSTEM SET recyclebin = OFF DEFERRED;
    ALTER SESSION SET recyclebin = off;
  3. Verify that the recycle bin is off using the following command:
    show parameter recyclebin;
Verify Linking for Shared Oracle Libraries
Shared Oracle libraries must be linked.
Follow these steps:
  1. Go to the instant client.
  2. Execute:
    ldd libociei.so
  3. Verify that there are links for all the libraries and that there are no
    not found
    messages. The output should look similar to the following:
    linux-vdso.so.1 +> (0x00007fff5b0e2000) libclntsh.so.11.1 => /root/instantclient_11_1/libclntsh.so.11.1 (0x00007f36030b3000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f3602eae000) libm.so.6 => /lib64/libm.so.6 (0x00007f3602c57000) libpthread.so.0 +> /lib64/libpthread.so.0 (0x00007f3602a3a000) libnsl.so.1 => /lib64/libnsl.so.1 (0x00007f3602821000) libc.so.6 => /lib64/libc.so.6 (0x00007f36024c1000) libnnz11.so => /root/instantclient_11_1/libnnz11.so (0x00007f3602064000) libaio.so.1 => /lib64.libaio.so.1 (0x00007f3601e61000) /lib64/ld-linux-x36-64.so.2 (0x00007f360a0a0000)
Manual Creation of the Tablespace and User
The procedure for creating a tablespace manually before running the installer is dependent on the version of Oracle that you will be using.
Create an Oracle 12c Database (Schema) Manually
Create a pluggable database using the files of a seed database. See the Oracle documentation for details about the options available when you create a database from a seed.
 
Follow these steps:
  1. Log in to the desired Oracle database as the administrator (sys as sysdba).
  2. Create a pluggable database. Execute the following statement, where
    <pdb_name>
    is the name of a pluggable database and <
    ts_name
    > is a tablespace name of your choice (for example,
    uim_ts)
    :
    create pluggable database <pdb_name> admin user <db_owner> identified by <owner_password> default tablespace <ts_name> datafile '<data_file_full_name.dbf>' size 500m autoextend on file_name_convert = ('<location_of_db_to_be_cloned>', '<location_of_new_pluggable_db>'); alter pluggable database <pdb_name> open;
  3. Connect to the pluggable database using 'sys as sysdba'. The service name for the pluggable database is the <
    pdb_name
    > created in the previous step.
  4. Create a non-administrator user in the UIM pluggable database. Execute the following statement, where <
    non-admin_owner
    > is the name of the user to be created:
    create user <non_admin_user> identified by <user_password>;
     
  5. Grant the necessary privileges to the local user <non_admin_user>.
    grant create session to <non_admin_user>; grant unlimited tablespace to <non_admin_user>; grant administer database trigger to <non_admin_user>; grant create table to <non_admin_user>; grant create view to <non_admin_user>; grant alter any table to <non_admin_user>; grant select any table to <non_admin_user>; grant create sequence to <non_admin_user>; grant create procedure to <non_admin_user>; grant create trigger to <non_admin_user>; grant create type to <non_admin_user>; grant under any type to <non_admin_user>; grant execute any type to <non_admin_user>; grant select on sys.v_$session to <non_admin_user>; grant execute on sys.dbms_lob to <non_admin_user>; grant execute on dbms_redefinition to <non_admin_user>; grant create any table to <non_admin_user>; grant drop any table to <non_admin_user>; grant drop any index to <non_admin_user>; grant drop any trigger to <non_admin_user>; grant lock any table to <non_admin_user>;
     
  6. Start the UIM Server installer. When prompted, enter the following information:
    • Service Name
      : Name of the pluggable database instance <
      pdb_name
      > you created.
    • Port
      : Port of the Oracle database.
    • Username
      : Username for local user <
      non_admin_user
      >.
Your database server is ready.
Create an Oracle 11g (or Earlier) Database Manually
Follow these steps:
  1. Log in as the Oracle administrator. 
  2. Create the tablespace. Execute the following statement, where
    <ts_name>
    is a tablespace name of your choice (typically
    CA_UIM)
    :
    create tablespace <ts_name> datafile '<ts_name>.dbf' size 1000m autoextend on maxsize unlimited;
  3. Create the owner and assign required privileges. Execute the following statement, where <
    db_owner
    > is the name of the user to be created and <
    ts_name
    > is the tablespace:
    create user <db_owner> IDENTIFIED BY <owner_password> DEFAULT TABLESPACE <ts_name>; grant unlimited tablespace to <db_owner>; grant administer database trigger to <db_owner>; grant create table to <db_owner>; grant create view to <db_owner>; grant alter any table to <db_owner>; grant select any table to <db_owner>; grant create sequence to <db_owner>; grant create procedure to <db_owner>; grant create session to <db_owner>; grant create trigger to <db_owner>; grant create type to <db_owner>; grant under any type to <db_owner>; grant execute any type to <db_owner>; grant select on sys.v_$session to <db_owner>; grant execute on sys.dbms_lob to <db_owner>; grant execute on dbms_redefinition to <db_owner>; grant create any table to <db_owner>; grant drop any table to <db_owner>; grant drop any index to <db_owner>; grant drop any trigger to <db_owner>; grant lock any table to <db_owner>;
    • The owner and tablespace
      commonly have the same name.
    • The
      grant unlimited tablespace
      command sets the quota for all tablespaces to unlimited. Although not tested by CA, you can set the quota for only the UIM database by executing the following statement in place of
      grant unlimited tablespace to <db_owner>
      :
      alter user <db_owner> quota unlimited on <ts_name>;