Home
Troubleshooting and Tuning
Performance depends on many factors, including your database and web server configuration, network connectivity and other configurations.
Troubleshooting Guide
Troubleshooting database issues
Refer to this section for assistance in troubleshooting database issues for Unica Campaign system tables and user tables (data sources).
Long-running campaign loses connection to database
You can set the STALE_CONN_TIMEOUT environment variable to automatically reconnect to a database if the Unica Campaign or Unica Optimize application loses connection to its back-end database.

Troubleshooting and Tuning
Performance depends on many factors, including your database and web server configuration, network connectivity and other configurations.
- Tuning Guide
- Troubleshooting Guide
  - Troubleshooting Unica Campaign Performance
    Performance depends on many factors, including your database and web server configuration, network connectivity, and Unica Campaign and Unica Platform configuration.
  - Using log files to troubleshoot
    These topics explain how to use the Unica Campaign log files for troubleshooting.
  - Unica Campaign Configuration
    These topics provide troubleshooting information about Unica Campaign configuration and integration.
  - Localization and Internationalization
    Refer to this section for assistance in troubleshooting issues with configuring Unica Campaign for use with non-ASCII data or non-United States locales.
  - Troubleshooting database issues
    Refer to this section for assistance in troubleshooting database issues for Unica Campaign system tables and user tables (data sources).
    - DB2 error message SQL1224N occurs on AIX
      Problem or error: The following DB2 error message occurs on AIX: SQL1224N A database agent could not be started to service a request
    - DB2 incompatibility with some ODBC drivers on 64-bit operating systems
      On 64-bit platforms, there are known compatibility issues between DB2 data sources and some ODBC drivers for Netezza, Teradata, and SQLServer. In these cases, DB2 cannot be used, either as a system tables data source or a user table data source, in combination with these databases.
    - Timeout and locking problems: DB2® database load utility
      Use the following suggestions to help troubleshoot timeout and locking problems that might occur when you use a DB2® database load utility with Unica Campaign.
    - "Check pending" problems: DB2® database load utility
      "Check pending" problems can occur when using a DB2® database load utility with Unica Campaign. Use the following suggestions to help troubleshoot these types of issues.
    - Error: SQL error when running the Financial Summary report on DB2
      Problem or error: The following error occurs when running the Financial Summary report on DB2: QE-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-9'. UDA-SQL-0107 A general exception has occurred during the operation "prepare". [IBM][CLI Driver][DB2] SQL0101N The statement is too long or too complex. SQLSTATE=54001
    - Oracle 10.2 client does not give permissions to others
      Problem or error: When you attempt to map tables using the Oracle 10.2 client, the process fails with a Library not found error. Table mapping succeeds if you change to the Oracle 10.1 client.
    - Oracle Error: ORA-01555: snapshot too old
      Problem or error: Errors occur during a Contact process cell execution.
    - Incorrect results from Select process with Netezza
      Problem or error: When Netezza is the user database and in-database optimization is not enabled in Unica Campaign, the Select process sometimes returns incorrect results.
    - Incorrect SHLIB_PATH for Teradata client TTU 8.1 on HP-UX
      Problem or error: The instructions given with the Teradata ODBC User's Guide are incorrect for the SHLIB_PATH for Teradata client TTU 8.1 on HP-UX.
    - Different languages for user tables are supported only if database is configured as UTF-8
      Unica Campaign supports a data source containing different languages for user tables only if the database is configured as UTF-8. SQLServer is not supported in multi-language configurations for user tables because it does not support UTF-8.
    - How to interpret the DBINFO entry in the data dictionary file
      Problem or error: What does the DBINFO entry in the data dictionary (.dct file) mean?
    - How Unica Campaign uses the TempFlag column
      Problem or error: What is the TempFlag column used for in the Unica Campaign system tables?
    - Long-running campaign loses connection to database
      You can set the STALE_CONN_TIMEOUT environment variable to automatically reconnect to a database if the Unica Campaign or Unica Optimize application loses connection to its back-end database.
  - Unica Campaign Server and Utilities
    Refer to this section for assistance in troubleshooting issues with the Unica Campaign utilities.
  - User Administration and Security
    Refer to this section for assistance in troubleshooting issues relating to application access and user permissions.
  - Unica Campaign Interface
    Refer to this section for assistance in troubleshooting issues with using the Unica Campaign interface.
  - Processes and Flowcharts
    Refer to this section for assistance in troubleshooting issues with Unica Campaign processes and flowcharts.
  - Cell Management
    Refer to this section for assistance in troubleshooting issues with cell management, including target cell spreadsheets, cell codes, and cell code formats.
  - Contact History and Response Tracking
    Refer to this section for assistance in troubleshooting issues with contact history and response tracking in Unica Campaign.
  - Stored Objects
    Refer to this section for assistance in troubleshooting issues with stored objects, including derived fields, user variables, custom macros, and templates.
  - Customizing campaigns
    Refer to this section for assistance in troubleshooting issues with customizing campaigns.
  - Installation and Upgrades
    Refer to this section for assistance in troubleshooting issues with installing and upgrading Unica Campaign.
  - Data Migration
    Refer to this section for assistance in troubleshooting issues with migrating and re-migrating data to Unica Campaign from pre-7.x versions of Affinium Unica Campaign.

Long-running campaign loses connection to database

You can set the STALE_CONN_TIMEOUT environment variable to automatically reconnect to a database if the Unica Campaign or Unica Optimize application loses connection to its back-end database.

An exception message similar to the following occurs: [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected: "<ip>". Communication function detecting the error: "send". Protocol specific error code(s):"32", "*", "0". SQLSTATE=08001.

This issue can occur when a long-running campaign loses connection to its database during a flowchart run.

Set the environment variable STALE_CONN_TIMEOUT for the listener script file for Unica Campaign or Unica Optimize. For example: STALE_CONN_TIMEOUT=<seconds>. The listener script file is rc.unica_ac/cmpServer.bat (for Unica Campaign) and ACOServer.sh/.bat (for Unica Optimize). It is located in <CAMPAIGN_HOME>\bin.

You must restart the listener after adjusting this parameter. If a connection is idle for the number of seconds defined, the connection will be re-opened. If a connection is lost, the following debug message appears in the Unica Campaign flowchart or Unica Optimize server log file: [DB QUERY] Connection is stale, so re-opening db connection!

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.