Creating ODBC or native connections

Create ODBC or native connections so that the Unica Campaign server can access the Unica Campaign database. Create ODBC or native connections on the computer where you installed the Unica Campaign server.

About this task

The computer on which the Unica Campaign server is installed must have an ODBC or native connection to the following databases:

  • The database or schema that contains the Unica Campaign system tables
  • The database or schema that contains the customer tables (sometimes called user tables).

Use the following guidelines to create these ODBC or native connections:

  • For databases on UNIX/SUSE: Create native connections for DB2® and Oracle databases or ODBC connections for other databases, such as Teradata, Netezza®. The procedure for creating a native data source differs depending on the data source type and the version of UNIX. See the data source and operating system documentation for specific ODBC driver installation and configuration instructions.
  • For databases on Windows: Create a new ODBC connection in the Control Panel Administrative Tools > Data Sources (ODBC) section.
  • For DB2® databases on z/OS®: The database user account must have SYSADM privileges. The DBADM privilege is not sufficient because it does not provide access to all of the required system objects.  Without SYSADM privileges, flowcharts might not run successfully.
  • For Oracle ODBC: For configuring your environment in ODBC, you will need to do following changes in environment:
    1. Install Unix ODBC driver version 2.3.7 or higher.
    2. Create System and User Datasource in odbc.ini file
      1. Edit odbc.ini file
      2. Add entry for system and User Datasource
      3. Make sure DSN entry, Servername in ODBC.ini file should be exactly matching to the DSN entry in tnsnames.ora file



        Driver = /u01/oracle19c/product/db_home/lib/

        Servername = orcl

        Port = 1521

  • For MariaDB: Set the following parameters in MariaDB configuration (.cnf or my.ini) file for Platform and Campaign.
    • Lower_case_table_names: The value is 1, so that table names are considered as case insensitive.
    • Set wait_timeout= <Time in seconds that the server waits for a connection to become active before closing it. The session value is initialized when a thread starts up from either the global value, if the connection is non-interactive, or from the interactive_timeout value, if the connection is interactive.>. For example: set this to 25,92,000 (seconds), in case the setup can be inactive for 30 days.
    • max_connections= <The maximum number of simultaneous client connections>.
    • innodb_strict_mode = 0
  • For Postgres : Set the following parameters in Postgres configuration (postgresql.conf) file for Platform and Campaign.
    • max_connections: set this value to 1000
      Note: While running application if there is error Campaign Server: loadFolderDetailItemsByEntity: Database connection error (Error Code = 11518). Please increase the value of parameter max_connections as per application usage.
Note: Unica Campaign supports certain versions of DB2® on z/OS® for customer tables only, not system tables. For more information, see the Recommended Software Environments and Minimum System Requirements.

Be sure to record the ODBC name in the Unica Campaign installation worksheet.