Known limitations in HCL Campaign 9.1.2

Campaign 9.1.2 includes the following known limitations.

Table 1. Campaign known limitations
ID Known limitation
217488 IBM can support the Database Loader for Redshift until the moment Campaign triggers the Loader Script. Any problems in execution of the loader script are not supported by IBM.
NA

Big data: To perform the UPDATE operation on any process boxes in a flowchart, ensure that your HIVE tables are configured as transactional tables such that they support the ACID property. This is a key feature introduced in HIVE version 0.14.

190621

Big data: Campaign with Hive big data as a user database does not support user table mapping with Base and Dimension levels up to the fourth level hierarchy.

If you map a Base record table with four levels of dimension tables in a Select process box, then build a query based on the fourth level Dimension table, the query fails with Error 11528. This issue should not affect big data users because multiple dimensions should not be needed. By definition, a big data source has a large table of records split across Hadoop nodes (such as HDFS).

185854 Big data: Campaign integration with Hadoop-based Hive big data as a user data source is not tested on MS Windows operating system.
194095 For Redshift database, the error message "Unsupported type timestamps with time zone" is displayed when exporting data from a Snapshot process box. Timestamp with timezone is an unsupported PostgreSQL data type on Amazon AWS.
194806 BLU: Snapshot process box execution fails with error when records are exported with option Replace All Records. The error occurs with BLU DB2 database and only when Replace All Records is selected. It does not occur for Append to Existing.
NA IBM Interact when configured with IBM WebSphere Application Server: You must configure IBM WebSphere JVM to use JDK 1.7. When IBM WebSphere Application Server 8.5.5.x is configured with JDK 1.7 and HTTPS communication, you must use IBM JAVA SDK version 7.0.8.10 or higher.
NA Using multiple SQL statements for raw SQL queries is not currently supported on big data user datasources. For related information, search the IBM Knowledge Center for Hive query language conformance.
195581 While running a Campaign flowchart, if listener crashes or is stopped, user is not able to access the running flowchart from the UI. Requests are being served by another node of the cluster but while accessing the flowchart, a pop-up message says "listener failover occurred..." It may be necessary to restart the master listener.
196487 DataDirect + Cloudera: Snapshot process box execution fails when some of the output table column fields are not mapped. This is related to a known issue with the Hive 0.14 database. Workaround: To extract fewer than the fields in the mapped database table, fill them with derived fields or uservars and fill them with the default desired values, such as NULL.
184919

Big data: Mail List process execution fails with error: unique constraint (UCDUC9111.CCONTACTHIST_PK) violated.

Mail List / Call List process box execution completes successfully when User Database table - Audience Level is BigInt. However:

  • When a user profile table contains Audience ID in Decimal format, this error will occur.
  • When a user profile table is created by export from File to Database then by default all numeric fields are created as Decimal.

For big data: The user profile database table audienceID should be of BigInt type when used with DB2 databases. If the user profile database table audienceID is Decimal, the Mail List / Call List process box execution will have errors.

186489

Big data: "Record exported = Unknown" is displayed on Snapshot process box if cell size Limit is used in preceding Select process box.

(1) Count of records is unknown when a Snapshot is populated through INSERT INTO SELECT FROM queries. If you want a record count, map it as Base table, in which case Campaign will compute the record count. (2) Count of records will be known and updated in case of loader (LOAD DATA) invocation. No need to map the table.

NA

Web application clustering is supported only for stand-alone Campaign (not integrated with other products). For example, do not configure a clustered web application environment if you currently use eMessage, Interact, Contact Optimization or Marketing Operations. Only Sticky sessions are supported. No session replication is done, as the focus is on scalability. Failover is not implemented.

NA

Flowchart annotations are not affected by zoom. You cannot resize annotations. Annotations do not appear in the panning area. Annotations can be moved out of the flowchart window and the only way to access them is to move the associated process box in the direction of the annotation, then drag the annotation back to the main flowchart area and move the process box back to its original position. If an annotation overlaps a process box, drag the annotation to another position.

176377

DB2 10.5 BLU for user DB: No indexing requirement for temp tables in Campaign datasource. DB2 10.5 (with BLU feature ON) does not require indexing in Campaign. Campaign has certain properties for datasources, such as TempTablePreTruncateRunScript, TempTablePostExecutionSQL, and PostTempTableCreateRunScript, where you can provide SQL or scripts to create indexes on user database tables. If you are using DB2 10.5 as a customer database, with the BLU feature ON, you do not need to configure any of these temp table properties.

NA

Dialog behavior: In certain cases, it is necessary to click twice in order to activate a field or change a field value.

NA

The monitorEnabledForEmessage configuration property in Campaign|monitoring is not currently used.

NA

Relevant products limitation: When offer management is performed from HCLMarketing Operations, the "relevant products" functionality, which relates product IDs to offers, is not available.

NA

Blank or incorrect results from derived fields in a Mail List process. This can occur in a process box that uses a derived field that calls a Generated field (UCGF) that changes value.

Do not use a UCGF in a Mail List derived field if the UCGF is not constant. Also, from the Parameters tab, do not create a derived field to call a UCGF to populate offer attributes.

For details, see the following Tech Note: http://g01zciwas018.ahe.pok.ibm.com/support/dcf/preview.wss?host=g01zcidbs003.ahe.pok.ibm.com&db=support/swg/istech.nsf&unid=C4A93DC0ED188D6985257A6B00699C45&taxOC=SSCKNRB&MD=2012/08/31%2015:08:35&sid=

NA

Profiling a Campaign Generated Field (UCGF) does not yield correct results. Some UCGFs have a value according to the cell or the offer being processed. For cell-related UCGFs, only the value associated with the first cell appears during profiling.

NA

The default value for a custom cell attribute does not appear when you open the target cell spreadsheet. Although the default value is not initially displayed, it will be used. The value can be displayed or changed by clicking or opening and editing the custom cell attribute in the target cell spreadsheet.

NA

The UA_UsrResponseType.Name field cannot contain a left parenthesis followed by a single quote.

NA

Use unique TempTablePrefix for each data source when mapping multiple data sources to same physical database.

If you mapped multiple data sources in Campaign to the same physical database, and you use the same TempTablePrefix for more than one of the data sources, when you use the cleanup utility to delete orphaned temp tables, it may falsely identify temp tables as orphaned, when they are in fact legitimate temp tables defined from a different Campaign data source.

Any deleted temp tables will automatically be recreated when you rerun affected flowcharts, but as a best practice, use a unique TempTablePrefix for each data source when mapping multiple data sources to the same physical database.

If the data sources defined in Campaign map to different schemas in the database, another solution is to ensure that the database user who runs the cleanup utility does not have privileges to drop tables in other schemas in the same database.

11162

Several dialogs that might not contain a large amount of data or are not commonly used cannot be resized or maximized.

17202

Error 19024: Cannot delete segment folder if the segment was deleted from the folder. A segment that is deleted from a folder remains as an inactive segment in the folder. Folders with inactive segments cannot be deleted. This is working as intended.

18991

If the same flowchart is edited in multiple locales, undesired behavior can occur. This situation occurs only if two (or more) users with different language settings edit the same flowchart. Users with different locales should not edit the same flowchart that was created by a user with a different locale since this can lead to undesired behavior. The preferred approach is to create and edit flowcharts with users having the same language settings.

84147

Copy and paste behavior in process boxes and other dialogs: For security reasons, some browsers do not allow applications to copy and paste via the Clipboard. This affects the General tab of the Segment process configuration and other areas of the application where copy and paste might be used.

161323

The error "Login failed. Error 10553" can occur if you try to log in to the Campaign utilities when the IBM Marketing Platform | Security | login method is set to Windows integrated login or Web access control. To avoid this issue, change the login type to LDAP or IBM Marketing Platform prior to using the Campaign utilities.

201968, 200241

If two process boxes are moved very close together in a flowchart, the direction of the connection arrow changes. This limitation affects the visual representation of the arrow. The process data flow is not affected. The workaround is to move the process boxes farther apart so the arrowhead changes back to the correct direction.