Data Migration Guidedoc.unica.com/products/campaign/8_5_0/en_us/IBMUni... · Data re-migration refers to the migration of the same object(s) from the source system to the target system

IBM Unica CampaignVersion 8.5.0 Publication Date: June 7, 2011

Data Migration Guide

Copyright

© Copyright Unica Corporation 2010.

Unica Corporation

Reservoir Place North

170 Tracer Lane

Waltham, MA 02451-1379

Examples and Data

All software and related documentation is subject to restrictions on use and disclosure as set forth inthe Unica Software License and Services Agreement, with restricted rights for U.S. governmentusers and applicable export regulations.

Companies, names, and used in examples herein are fictitious unless otherwise noted.

Trademarks and Patents

Unica, the Unica logo, NetInsight, Affinium and MarketingCentral are registered trademarks of UnicaCorporation with the U.S. Patent and Trademark Office. MARKETING SUCCESS STARTS WITH Uis a trademark. All other trademarks are the property of their respective owners.

Portions of the software described in this document are covered by U.S. Patent Numbers: 6,317,752,6,269,325, 6,542,894, and 6,782,390.

The NetTracker and Unica NetInsight products are licensed under the following patents and patentpublications: US5,675,510, US6,115,680, US6,108,637, US5,796,952, US6,138,155, US6,653,696,US6,763,386, AU0701813, BR9609217, CA2223919, EP0843946, JP03317705, MX193614,NO09705728, AU735285, CA2246746, CN1174316, CN1547123, CN1547124, DK870234,DE69720186, ES2195170, AU727170, BR9808033, CA2284530, CN1251669, IL131871,JP2000514942, KR341110, NZ337756, WO9641495, EP0870234, EP1130526, EP1168196,US20040078292, WO9810349, US20050114511, US20040221033, WO9843380.

Markup functionality in Unica Marketing Operations is enabled through use of third-party softwarecomponents from AdLib™ eDocument Solutions and Adobe® Acrobat®. "Powered by AdLib™."

NOTICE: This document contains confidential and proprietary information of Unica Corporation("Unica"). Use, duplication, or disclosure without the express written consent of Unica Corporation isprohibited.

Table of Contents

Preface Contacting IBM Unica technical support .....................................................................................6

1 Introduction to Data Migration in Unica Campaign .................................................8Overview of data migration ................................................................................................................... 8

What is data migration? ........................................................................................................................ 8

Which versions of Campaign require data migration?..........................................................................9

What is data re-migration?.................................................................................................................... 9

Re-migration modes.......................................................................................................................... 9

About the data migration stages.........................................................................................................10

Data migration limitations.................................................................................................................... 10

System compatibility ........................................................................................................................... 11

File system accessibility......................................................................................................................11

System table accessibility and permissions........................................................................................12

Knowledge requirements .................................................................................................................... 12

Required upgrades and installations ..................................................................................................12

2 Preparing the Data Migration Environment ............................................................14Preparing the source and target systems...........................................................................................14

Install the required software versions .................................................................................................14

Map the system tables........................................................................................................................ 15

Create the required partitions on the target system ...........................................................................15

Set environment variables ..................................................................................................................15

Environment variables required for data migration .........................................................................16

Set database ID limits......................................................................................................................... 21

Guidelines for setting database ID limits ........................................................................................21

Set code formats on the target system...............................................................................................22

Create required audience levels on the target system .......................................................................22

Create additionally tracked fields on the target system......................................................................22

Verify system table compatibility.........................................................................................................22

Create the pathmap file (Campaign 6.2.x or earlier versions only) ....................................................23

Entries required in the pathmap file ................................................................................................23

Version 8.5.0 3

Database driver requirements for migrating data from 32-bit to 64-bit versions ................................24

Preparing a distributed environment on multiple operating systems..................................................24

For source systems with Affinium Security Manager 6.x................................................................24

For source systems with Affinium Manager 7.x ..............................................................................25

3 Migrating Data ...........................................................................................................27Before you migrate data ..................................................................................................................... 27

About web application server status during data migration ................................................................27

About migrating multiple partitions......................................................................................................28

About the data migration log...............................................................................................................28

Cancelling data migration ................................................................................................................... 29

Run the data migration scripts ............................................................................................................29

Guidelines for running the data migration scripts ...........................................................................29

Stage 1 – Setup .............................................................................................................................. 30

Stage 2 – Consistency checks........................................................................................................32

Stage 3 – File system artifacts........................................................................................................33

Stage 4 – Database artifacts ..........................................................................................................34

Stage 5 – Offer, campaign, and session artifacts...........................................................................34

Stage 6 – Finish data migration ......................................................................................................36

Import the Platform configuration file (distributed environment on multiple operating systems withAffinium Manager 7.x only) ................................................................................................................ 37

Verify data migration........................................................................................................................... 37

About migration results ....................................................................................................................... 37

4 Data Migration Reference.........................................................................................39Introduction ......................................................................................................................................... 39

Campaigns.......................................................................................................................................... 40

Cells .................................................................................................................................................... 40

Configuration settings ......................................................................................................................... 40

Contact and response history .............................................................................................................41

Control groups .................................................................................................................................... 43

Cubes and strategic segments ...........................................................................................................43

Custom attributes................................................................................................................................ 44

Custom macros................................................................................................................................... 46

Derived fields ...................................................................................................................................... 46

Dimension hierarchies ........................................................................................................................ 46

Flowcharts........................................................................................................................................... 47

4 IBM Unica Campaign - Data Migration Guide

Flowchart templates............................................................................................................................ 47

Folders ................................................................................................................................................ 48

Initiatives ............................................................................................................................................. 48

Offers .................................................................................................................................................. 48

Offer templates ................................................................................................................................... 49

Offer versions...................................................................................................................................... 50

Processes ........................................................................................................................................... 50

Security ............................................................................................................................................... 53

Sessions ............................................................................................................................................. 53

Table catalogs..................................................................................................................................... 54

Triggers............................................................................................................................................... 54

5 Troubleshooting ........................................................................................................56Troubleshooting .................................................................................................................................. 56

Snapshot process that accepts a Score output cell as input appears unconfigured after it ismigrated .............................................................................................................................................. 56

New folders on the source system do not appear on the target system after data re-migration........57

Inferred response history records are migrated as direct responses .................................................57

Stage 2 error after re-running Stage 5................................................................................................57

Stage 2 consistency check fails for a campaign or session when the lock file is missing .................58

Stage 3 fails to create default offer template ......................................................................................58

Stage 5 fails to migrate contact and response history records prior to year 2000 .............................59

Error when migrating or re-migrating flowcharts.................................................................................60

AGFs associated with retired features and migrated through a template fail to run ..........................60

Warning when migrating data from Campaign 5.1.1 ..........................................................................61

A Customizing Data Migration ....................................................................................62About customizing data migration.......................................................................................................62

Example custom data migration tasks ................................................................................................62

Implementing a custom task ...............................................................................................................63

To add a custom task to a data migration stage ............................................................................63

Information required for adding data migration tasks .....................................................................63

Removing a custom task from a data migration stage .......................................................................64

Running a customized data migration stage script.............................................................................64

Sample Java classes for implementing data migration tasks.............................................................64

Version 8.5.0 5

N10014

Preface

■ Contacting IBM Unica technical supportN40001

Contacting IBM Unica technical supportIf you encounter a problem that you cannot resolve by consulting the documentation,your company’s designated support contact can log a call with IBM Unica technicalsupport. Use the information in this section to ensure that your problem is resolvedefficiently and successfully.

If you are not a designated support contact at your company, contact your IBM Unicaadministrator for information.

Information you should gatherBefore you contact IBM Unica technical support, you should gather the followinginformation:

• A brief description of the nature of your issue.

• Detailed error messages you see when the issue occurs.

• Detailed steps to reproduce the issue.

• Related log files, session files, configuration files, and data files.

• Information about your product and system environment, which you can obtain asdescribed in "System Information" below.

System informationWhen you call IBM Unica technical support, you might be asked to provide informationabout your environment.

If your problem does not prevent you from logging in, much of this information isavailable on the About page, which provides information about your installed IBM Unicaapplications.

You can access the About page by selecting Help > About. If the About page is notaccessible, you can obtain the version number of any IBM Unica application by viewingthe version.txt file located under each application’s installation directory.


Contacting IBM Unica technical support

Contact information for IBM Unica technicalsupportFor ways to contact IBM Unica technical support, see the IBM Unica Product TechnicalSupport website: (http://www.unica.com/about/product-technical-support.htm).

Version 8.5.0 7

http://www.unica.com/about/product-technical-support.htm

N1001B

1 Introduction to DataMigration in UnicaCampaign

■ Overview of data migration■ What is data migration?■ Which versions of Campaign require data migration?■ What is data re-migration?■ About the data migration stages■ Data migration limitations■ System compatibility■ File system accessibility■ System table accessibility and permissions■ Knowledge requirements■ Required upgrades and installations

N50001

Overview of data migrationThis section provides an overview of the data migration process for Campaign.

For best results, engage with IBM Unica Consulting Services before performing anydata migration tasks in Campaign.

N60001

What is data migration?Data migration refers to the moving of data from a source version to a new targetinstallation of Campaign in a different location. You migrate data by running a set ofdata migration scripts provided with your IBM Unica Marketing installation.

When you perform data migration, the configuration settings, files, and data are copiedfrom your source Campaign system to the new target system. The data migrationprocess does not modify any source data or configuration files.

For details on migration of specific object types, see the topic for each object type in theData Migration Reference chapter.


Which versions of Campaign require data migration?

N70001

Which versions of Campaign require datamigration?

Data migration is required to move from Affinium Campaign 5.1+ or 6.x to Campaign.Before you can perform data migration, you must successfully install the new version ofCampaign in a different location from your source version. For details, see theinstallation documentation. There is no option to perform an in-place upgrade from apre-7.x version of Affinium Campaign to Campaign.

If your source version of Campaign is 7.x, you do not need to migrate your data toupgrade to Campaign. To upgrade from a 7.x source version to Campaign, perform anin-place installation of Campaign over your source version. There is no option to installan empty instance of Campaign and perform data migration of objects from AffiniumCampaign 7.x.

N80002

What is data re-migration?Data re-migration refers to the migration of the same object(s) from the source systemto the target system multiple times. This process might be required if any objects(campaigns, sessions, flowcharts, or offers) cannot immediately be made production-ready in the new system, and must continue to operate and be modified in a sourcesystem until another data migration attempt is made. The migration of most content isone-time only (for example, users, groups, configuration, templates, table catalogs, andso on).

For details on re-migration of specific object types, see the topic for each object type inthe Data Migration Reference chapter.

N110001

Re-migration modesWhen you select an object for re-migration, you can choose one of the following modes:

• Overwrite (replace) — In this mode, if the selected objects already exist in thetarget system, they are updated, except if treatments for a re-migrated offer exist inthe target system. If treatments exist in the target system for an offer, that offer willnot be re-migrated and a warning is written to the migration log.

• Skip (preserve) — In this mode, only new objects are migrated. Objects selectedfor re-migration that already exist in the target system are not overwritten in thetarget system. This mode allows you to continue using the source system while youvalidate the target system. After you are sure that the target system is working, youcan migrate any new objects to the target system before you take the source systemoffline.

Version 8.5.0 9

1 - Introduction to Data Migration in Unica Campaign

If an object selected for re-migration has been edited in the target system, changesto the object in the target system will be lost if the Overwrite mode is selected. Topreserve these changes, select the Skip mode.

N90001

About the data migration stagesThe Campaign data migration process consists of six distinct stages, each oneexecuted by a separate script. The scripts are installed in thetools/migration/5.1+To8.5 folder when you run the Campaign Utililty Toolsinstaller. For details, see the IBM Unica Campaign Installation Guide.

For each partition in your environment, run the six scripts in sequence to migratesystem table data and all of the corresponding underlying objects.

Before executing any of the scripts, you must understand the purpose of each stage ofdata migration, which scripts can be run multiple times, and so on.

Stage 2 can be run multiple times for the same partition, but not after Stages 3 or 4have run. Alternatively, Stage 2 can be run from within Stage 5.

Stage 5 can be run multiple times for the same partition to re-migrate objects, but onlyafter running Stage 4 and before running Stage 6.

All other stages can be run only once, except in the case where the script fails tocomplete. You should not run Stage 6 until you are sure you have successfullycompleted data migration for the partition.

The six stages are as follows:

• Stage 1 — Setup

• Stage 2 — Perform consistency checks

• Stage 3 — Copy file system artifacts and system configurations

• Stage 4 — Copy database artifacts

• Stage 5 — Copy offer, campaign, and session artifacts

• Stage 6 — Finish data migration and clean up temporary files

In addition to the default tasks provided in the data migration stages, Campaignprovides a utility that allows you to customize the workflow of migration Stages 2–5 byadding or removing data migration tasks. For details, see Customizing Data Migration.

NA0002

Data migration limitationsThe Campaign data migration process has the following limitations:


System compatibility

• It does not support “in place” data migration; that is, data is not migrated within thesame instance of IBM Unica Campaign. Use the data migration tool only if you haveinstalled the new version of Campaign in a different location from your existingversion.

• It does not copy database configuration from the source to the target system tables.In particular, the following configurations are not migrated:

• Database-specific scaling and performance features (such as DB2 partitions).

• Existing constraints/indexes on system tables in the source database. You mustre-create the constraints/indexes manually if you want them in the target tables.

• It does not copy any folders other than those originally installed by a Campaigninstallation to <CAMPAIGN_HOME>/partitions/partition[n].

• It does not allow changes to the policy ID of objects between data re-migration runs.All objects will be migrated with the single policy ID chosen during Stage 1. For thisreason, no changes should be made (directly or implicitly) to policy IDs assigned tovarious objects.

Some types of data, including object types, files, and configuration settings, also havespecific migration limitations and requirements. For details, see the specific topics in theData Migration Reference chapter.

NB0001

System compatibilityYour source and target Campaign installations must match in the following ways:

• They must be installed on the same type of operating system.

• They must use the same database type and version for their system tables.

• Their database tables must be in the same database instance.

• They must be deployed on the same type of web application server.

If you need to change any of these components (for example, upgrade the database),you must perform the upgrade on the source system prior to beginning data migration,or after data migration is complete.

NC0001

File system accessibilityThe Campaign source file system must be visible from the target Campaign system.Therefore, either both versions of Campaign must be hosted on the same machine, orboth the Campaign and Affinium Security Manager 5.1+/6.x root directories must beadded as a shared drive/NFS mount on the machine where you run the IBM UnicaCampaign data migration scripts.

ND0001

Version 8.5.0 11

1 - Introduction to Data Migration in Unica Campaign

System table accessibility and permissionsThe Campaign system tables have the following accessibility and permissionrequirements:

• The target Campaign system tables must be in the same database and databaseserver instance as the source Campaign system tables. That is, it must be possibleto SELECT from the source tables and INSERT into the target tables.

• The database login you provide to the data migration scripts must be able toSELECT from the source system tables and SELECT from and INSERT into thetarget system tables. For example, on an Oracle database, the equivalent of astatement such as GRANT SELECT ON UA_SrcTableName TO UC8DbUser must beexecuted for all of the Campaign system tables (for example, UA_Folder) in thesource Campaign system database before you perform data migration.

• The data migration tool creates temporary tables in the same schema as the systemtables in the target partition you specify. These temporary tables are usedthroughout the data migration and are then dropped in the final step, after you havefinished migrating all data for the selected partition. The database login you provideto the data migration scripts must have the same or greater privileges as the userwho created the target Campaign system tables.

NE0001

Knowledge requirementsThe instructions in this guide assume that the person performing the data migration hasan understanding of the following:

• General IBM Unica Campaign functionality and components, including the structureof the file system.

• The installation and configuration process for the source and target versions ofCampaign.

• The installation and configuration process for the source version of Affinium SecurityManager and for the IBM Unica Marketing Platform.

• The functionality and usage of Affinium Security Manager on the source system.

• How to manage configurations in IBM Unica Marketing Platform.

• The installation and configuration process for IBM Unica reporting, if you are usingIBM Unica reports.

• Viewing and working with database tables.NF0002

Required upgrades and installationsYou must perform the following tasks before migrating data to Campaign.


Required upgrades and installations

• Upgrade to Marketing Platform . To upgrade from Affinium Security Manager, youmust first upgrade to Affinium Manager 7.5.1, and then upgrade to MarketingPlatform. For instructions, see the Marketing Platform Installation Guide.

• Install, deploy, and configure Campaign . Install Campaign in a different locationfrom your Affinium Campaign source system. For instructions, see the CampaignInstallation Guide.

• Install the data migration utilities. For instructions, see the Campaign InstallationGuide.

Version 8.5.0 13

N10065

2 Preparing the DataMigrationEnvironment

■ Preparing the source and target systems■ Install the required software versions■ Map the system tables■ Create the required partitions on the target system■ Set environment variables■ Set database ID limits■ Set code formats on the target system■ Create required audience levels on the target system■ Create additionally tracked fields on the target system■ Verify system table compatibility■ Create the pathmap file (Campaign 6.2.x or earlier versions only)■ Database driver requirements for migrating data from 32-bit to 64-bit

versions■ Preparing a distributed environment on multiple operating systems

N130002

Preparing the source and target systemsThis section describes the tasks required for preparing the source and target systemsfor migrating data.

N140002

Install the required software versionsBefore you can migrate data to Campaign, the following upgrades and installations mustbe performed:

• Upgrade from Affinium Security Manager to Affinium Manager 7.5.1 beforeupgrading to IBM Unica Marketing Platform. This is required because you canupgrade to IBM Unica Marketing Platform only from Affinium Manager 7.5.x. Toupgrade from Affinium Security Manager, see the instructions for upgrading from7.3.1 and earlier versions of Affinium Manager in the IBM Unica Marketing PlatformInstallation Guide.


Map the system tables

• Upgrade from Affinium Manager 7.5.1 to IBM Unica Marketing Platform. For details,see the IBM Unica Marketing Platform Installation Guide.

• Install the Campaign target system in a different location from the source version.Ensure that the target system has full access to the source system. For details, seethe IBM Unica Campaign Installation Guide.

• Install the data migration tools using the Campaign Utility Tools installer. For details,see the IBM Unica Campaign Installation Guide.

N150001

Map the system tables1. Ensure that all of the system tables on the source system have been mapped,

including any that have not been used.

2. Map all of the system tables on the target system.

eMessage and Optimize tables can be left unmapped if eMessage and Optimizeare not installed.

For information on mapping tables, see the IBM Unica Campaign Administrator’sGuide.

N160001

Create the required partitions on the targetsystem

If your source system has multiple partitions, create the same number of partitions onthe target system.

For information on creating and configuring multiple partitions, see the installationdocumentation.

N170001

Set environment variablesEdit the setenv file on the target system to set environment variables required by thedata migration scripts. The setenv file is located in thetools/migration/5.1+To8.5 directory in the path where you have installed thedata migration tools on the target system.

YES and NO values for environment variables must be entered in uppercase.

UNIX only: After editing the setenv file, run the file using the following command to setthe variables:

. ./setenv

N200002

Version 8.5.0 15

2 - Preparing the Data Migration Environment

Environment variables required for data migrationThe following environment variables must be set on the Campaign target system. Notethat many of these variables are set automatically for you by the Campaign installer;however, you should review the setenv file prior to upgrading to verify that each settingis correct for your specific upgrade scenario. The instruction comments contained in thesetenv file itself describe each setting and can help you complete any values relevantto your installation.

Variable Description

UNICA_PLATFORM_HOME Root directory of the IBM Unica Marketing Platform installation.Examples:

Windows

set UNICA_PLATFORM_HOME="C:\Unica\Platform"

UNIX

UNICA_PLATFORM_HOME='/Unica/Platform'

export UNICA_PLATFORM_HOME

CAMPAIGN_HOME Home directory of your IBM Unica Campaign installation.Examples:

Windows

set CAMPAIGN_HOME="C:\Unica\Campaign"

UNIX

CAMPAIGN_HOME='/Unica/Campaign'

export CAMPAIGN_HOME

JAVA_HOME Root directory of the JDK used by your Campaign installation.

For WebLogic 10gR3 or higher, which uses JDK1.6, you mustprovide the JAVA_HOME path to JDK1.6; the upgrade tool utilityfails if provided with a JAVA_HOME other than JDK1.6.

Examples:

Windows

set JAVA_HOME="C:\Program Files\bea\jdk150_14"

UNIX

JAVA_HOME='/bea/jdk150_14'

export JAVA_HOME


Set environment variables


LOG_TEMP_DIR Directory where you want the data migration scripts to createlog files. Examples:

Windows

set LOG_TEMP_DIR=C:\temp

UNIX

LOG_TEMP_DIR='/var/tmp'

export LOG_TEMP_DIR

ERROR_MSG_LEVEL Desired logging level. Valid values, listed from most to leastverbose, are:

DEBUG

INFO

ERROR

FATAL

JDBCDRIVER_CLASSPATH Full path for the JDBC drivers, including the complete .jar filefilename.

For both Weblogic and WebSphere, the path needs to includethe .jar file.

For DB2 9.1, you must specify db2jcc.jar anddb2jcc_license_cu.jar.

MIGRATE_FLOWCHART_ Types of flowcharts to migrate. Keep the default value set toBatch .

TYPES

Valid values are "Batch", "Event Processing" and"Batch,Event Processing" (quotation marks are requiredfor Event Processing). However, migration of event processing(i.e., interactive) flowcharts is not currently supported. Thesevalues are for future compatibility only.

IsPartitionsSupported Indicates whether the source installation of Campaign supportspartitions. Valid values are YES and NO .

IsSkipEnvironmentVars For source installations of Campaign that do not supportpartitions, the IsSkipEnvironmentVarsPrompt indicates

Prompt whether you want the Stage 1 script to prompt for theenvironment variables. Valid values are YES and NO . If set toYES , the Stage 1 script will not prompt for these values, andthe default values will be used.

If the IsPartitionsSupported variable is set to YES , thissetting is ignored.

Version 8.5.0 17



STRING_MAP_INFO_FILE Location of the locale-specific message mapping file. Exam-ples:

Windows

set

STRING_MAP_INFO_FILE="C:\Unica\Campaign\tools\

migration\ 5.1+To8.5\stringsmap.xml"

UNIX

set

STRING_MAP_INFO_FILE='\Unica\Campaign\tools\

migration\5.1+To8.3\stringsmap.xml'

export STRING_MAP_INFO_FILE

IGNORE_SES_TEMP_FILES Indicates whether temporary session files (indicated by anunderscore character at the beginning of the file name) will becopied. A YES setting specifies that these files will not becopied. The default value is NO .

SOURCE_SYSTEM_VERSION Version number of your Campaign source system (for exam-ple, 5.2.2, 6.4.10).


Set environment variables


OFFER_VERSION_COUNT_ It is necessary to change this property only if your sourcesystem data uses the underscore character in offer codes or

SEPARATOR offer version codes. The default value is underscore (_). Youcan set this property to any character or character combinationthat is not used in either the offer codes or the offer versioncode values in the source system tables.

Before using the data migration scripts, we recommend thatyou confirm in advance that the chosen separator characterdoes not exist in the source system tables. The SQL statementin the following example for a DB2 database checks for theexistence of the underscore character in offer codes and offerversion codes:

SELECT COUNT(*) FROM UA_Offer WHERE

OfferCode1 LIKE '%\_%' ESCAPE '\' OR





VersionCode LIKE '%\_%' ESCAPE '\'

If the SQL example above returns no matching rows, then thedefault offer version count separator character may be used. Ifmatching rows are found, then this statement should bemodified to check for other characters until a suitable characteris found.

PATH (all UNIX versions only) Add the Campaign bin directory and the migration toolsdirectory to the PATH variable. The following example showsthe path with tools installed in a directory called Migration atthe root directory:

PATH=${CAMPAIGN_HOME}/bin:/Migration/tools/mig

ration/5.1+To8.5:${PATH}

export PATH

Version 8.5.0 19



LD_LIBRARY_PATH (Solaris The LD_LIBRARY_PATH variable (Solaris) or LIBPATH vari-only), LIBPATH (AIX only) able (AIX) in the tools/migration/5.1+To8.5 directory

should match the LD_LIBRARY_PATH or LIBPATH setting inthe setenv file in the Campaign bin directory. Add thevariable to the setenv file in thetools/migration/5.1+To8.5 directory and include thefollowing:

• Path to the Campaign bin directory• For Oracle only: ORACLE_HOME and ORACLE_BASE

The following example shows the requiredLD_LIBRARY_PATH settings for a Solaris environment with anOracle 10.2 database:

ORACLE_BASE=/opt/oracle10.2

export ORACLE_BASE

ORACLE_HOME=/opt/oracle10.2

export ORACLE_HOME

LD_LIBRARY_PATH=/Unica/Campaign/bin:/opt/

oracle10.2/lib:/usr/lib

export LD_LIBRARY_PATH

JAVA_OPTIONS Optional: Specifies the minimum and maximum heap memoryto be assigned to Java Virtual Machine (JVM). This variable isdisabled (commented out) by default.

If you receive memory errors when running the data migrationscripts, uncomment this variable and set it before rerunningthe scripts.

Example:

JAVA_OPTIONS="-Xms256m -Xmx512m"

UNICA_ACSYSENCODING (for Set to the value of the system_string_encoding propertymigrating non-ASCII data in the unica_aclsnr.cfg file on the source system.only)

NLS_LANG (for migrating non- Set to AMERICAN_AMERICA.UTF8

ASCII data on Oracle data-bases only)

DB2CODEPAGE (for migrating Set according to the database settings on the target system.non-ASCII data on DB2 data-bases only)

N180001


Set database ID limits

Set database ID limitsTo prevent ID conflicts, the range of IDs in the source and target systems must notoverlap. IDs from the source system are copied over directly, and the data migrationalso creates some new objects that require IDs.

Set the database ID limits for each partition using the internalIdLowerLimit andinternalIdUpperLimit properties on the Configuration page.

For information on setting configuration properties, see the installation documentation.N210002

Guidelines for setting database ID limitsFollow these guidelines for data migration when setting the database ID limit propertiesfor the source and target systems.

Source system

Property Guidelines

internalIdLowerLimit Optional

internalIdUpperLimit This property must:

• be higher than the lower ID limit;• be higher than the highest ID used in the source system

tables; and• allow some unused IDs for new objects to be created (if

the source system remains in use after initial data migra-tion).

Target system

Property Guidelines

internalIdLowerLimit This property must be higher than the upper ID limit in thesource system.

internalIdUpperLimit Optional. If you set this property, it must:

• be higher than the lower ID limit in the target system;• be higher than the highest ID that will be used in the target

system tables; the default largest value ( 4294967295) issufficient in most cases

N190001

Version 8.5.0 21


Set code formats on the target systemCode formats for generated codes in the target Campaign system (cell codes, offercodes, and campaign codes) must be the same as, or compatible with, the generatedcode formats in your source Campaign installation.

For Affinium Campaign 6.4 and previous versions, the default value ofcellCodeFormat is Annn. If you are using this default value on the source system,make sure to change the value on the target system to Annn (the default value ofcellCodeFormat on the target Campaign system is Annnnnnnnn).

N1A0001

Create required audience levels on thetarget system

All audience levels referenced in templates must first be manually created in the targetCampaign environment. Follow these guidelines:

• Make sure that all necessary system tables are configured and mapped for eachaudience level before you move the templates to the target system.

• Set up the audience levels and their required database tables and table mappings tomatch the audience levels on the source system.

• If you have multiple audience levels mapped to the same contact or responsehistory table, you must use views that contain only the rows used by the individualaudience levels.

For information on creating audience levels, see the Campaign Administrator's Guide.N1B0001

Create additionally tracked fields on thetarget system

The data migration scripts do not add user-defined additionally tracked fields to anydatabase tables. Before performing data migration, you must ensure that all user-defined additionally tracked fields in the source system are defined in the target system.Create and map the fields on the target system using the names and types that matchthose on the source system.

For more information on additionally tracked fields, see the Campaign User's Guide.N1C0002

Verify system table compatibilityEnsure compatibility between the Campaign system tables on your source and targetsystems:


Create the pathmap file (Campaign 6.2.x or earlier versions only)

• User-defined fields in the Campaign system tables on your target system (forexample, in your contact history, response history and product tables) must becompatible with the equivalent fields in your source Campaign installation. Theymust have the same data type and width.

• The contact history and response history tables on your target system must containeither user-defined columns or a column named UserDefinedField.

• The login that you specify in your application server’s JDBC data sourceconfiguration (either in Weblogic’s JNDI specification, or directly using the inputprompts in the data migration scripts) must be able to access the system tables inboth your source installation and your Campaign target installation.

N1D0001

Create the pathmap file (Campaign 6.2.x orearlier versions only)

If your source version of Campaign is 6.2.x or earlier, you must create a pathmap file tomap Campaign directories from your source system to your target system.

Each line in the pathmap file contains two directory paths (source system path andtarget system path) separated by a single <tab> . Save the file with the file namepathmap (no extension) to the<CAMPAIGN_HOME>/partitions/partition[n]/conf directory on your targetsystem.

N220001

Entries required in the pathmap fileThe pathmap file must contain the following entries:

UNICA_UDICATDIR <partition home>/<partition[n]>/catalogs

UNICA_ACCUBEDIR <partition home>/<partition[n]>/cubes

UNICA_ACFTPDIR <partition home>/<partition[n]>/ftp

UNICA_ACSEGDIR <partition home>/<partition[n]>/segments

UNICA_ACTPLDIR <partition home>/<partition[n]>/templates

UNICA_CAMPAIGNROOTDIR <partition home>/<partition[n]>/campaigns

UNICA_SESSIONROOTDIR <partition home>/<partition[n]>/sessions

UNICA_UDICATDIR <partition home>/<partition[n]>/catalog

UNICA_ACLOGDIR <partition home>/<partition[n]>/logs

If you have subdirectories under the above directories, you must list them as well. Forexample, if you have Q1 , Q2 , Q3 and Q4 directories underUNICA_CAMPAIGNROOTDIR, add the following entries to the pathmap file:

<UNICA_CAMPAIGNROOTDIR>/Q1 <partition

home>/<partition[n]>/campaigns/Q1

Version 8.5.0 23








N1E0001

Database driver requirements for migratingdata from 32-bit to 64-bit versions

If you are moving from a 32-bit to a 64-bit version of IBM Unica Campaign, yourenvironment must meet the following requirements:

• The database drivers for your Campaign data sources must be 64-bit.

• All relevant library paths (for example, startup or environment scripts) must correctlyreference the 64-bit versions of your database drivers.

N1F0001

Preparing a distributed environment onmultiple operating systems

If your Campaign web application, Campaign analytical server (containing theCampaign listener), and the Marketing Platform are installed on different operatingsystems (for example, Campaign web application and Platform on Windows andCampaign analytical server on UNIX), you must perform additional steps to prepareyour environment for data migration. These steps vary depending upon whether yoursource system has been upgraded from Affinium Security Manager 6.x to AffiniumManager 7.x.

N230001

For source systems with Affinium SecurityManager 6.x1. Install the data migration tools on the Campaign analytical server target system. For

information on installing the data migration tools, see the IBM Unica CampaignInstallation Guide.

All data migration tasks are performed on the Campaign analytical server. Themigration tools are not required on the Campaign web application server.


Preparing a distributed environment on multiple operating systems

2. Copy the database templates for all of the database types in your Campaignenvironment (for example, DB2Template.xml, OracleTemplate.xml,SQLServerTemplate.xml) from the <CAMPAIGN_HOME>/conf directory on theCampaign web application target system to the <CAMPAIGN_HOME>/conf directoryon the Campaign analytical server target system. These template files are requiredfor migration Stage 3.

3. Make the following changes to the setenv file in the<MIGRATION_TOOLS_HOME>/tools/migration/5.1+To8.5 directory:

a. Set the JAVA_HOME property to the JRE on the Campaign analytical servertarget system (<CAMPAIGN_HOME>/jre).

b. Set the UNICA_PLATFORM_HOME property to the same directory asCAMPAIGN_HOME.

4. Create an authorization/confdata directory under the <CAMPAIGN_HOME>

directory on your Campaign analytical server target system.

5. Copy the affinium_config.xml file from Affinium Security Manager to the<CAMPAIGN_HOME>/authorization/confdata directory that you created on theCampaign analytical server target system. This file is required for migration Stages 1and 3.

N240001

For source systems with Affinium Manager 7.x1. Use the configTool utility on your Marketing Platform system to export the

<PLATFORM_HOME>/conf/Manager_config.xml file to a different location.

This step is required because the migration stages overwrite your desired Platformsettings with the settings in the affinium_config.xml file. (You will add theaffinium_config.xml file to your Campaign analytical server in a later step.) Torestore your desired configuration settings after completing data migration, you willneed to import your saved Manager_config.xml file.

For information on using the configTool utility, see the IBM Unica MarketingPlatform Administrator's Guide.

2. Install the data migration tools on the Campaign analytical server target system. Forinformation on installing the data migration tools, see the IBM Unica CampaignInstallation Guide.

All data migration tasks are performed on the Campaign analytical server. Themigration tools are not required on the Campaign web application server.

3. Copy the database templates for all of the database types in your Campaignenvironment (for example, DB2Template.xml, OracleTemplate.xml,SQLServerTemplate.xml) from the <CAMPAIGN_HOME>/conf directory on theCampaign web application target system to the <CAMPAIGN_HOME>/conf directoryon the Campaign analytical server target system. These template files are requiredfor migration Stage 3.

Version 8.5.0 25


4. Make the following changes to the setenv file in the<MIGRATION_TOOLS_HOME>/tools/migration/5.1+To8.5 directory:

a. Set the JAVA_HOME property to the JRE on the Campaign analytical servertarget system (<CAMPAIGN_HOME>/jre).

b. Set the UNICA_PLATFORM_HOME property to the same directory asCAMPAIGN_HOME.

5. Create an authorization/confdata directory under the <CAMPAIGN_HOME>

directory on your Campaign analytical server target system.

6. Obtain a copy of the affinium_config.xml file from Affinium Security Manager(this file does not exist in Affinium Manager 7.x). This file is required for migrationStages 1 and 3.

You can obtain this file from a backup of Affinium Security Manager 6.x or fromUnica technical support. Alternatively, you can create your own file, but you mustensure that it is compatible with Affinium Security Manager authentication. For moreinformation, see the Affinium Security Manager 6.x documentation.

7. Copy the affinium_config.xml file to the<CAMPAIGN_HOME>/authorization/confdata directory that you created on theCampaign analytical server target system.

You can ignore the settings in the affinium_config.xml file; after datamigration, you will overwrite them with the contents of your savedManager_config.xml file.


N100D6

3 MigratingData

■ Before you migrate data■ About web application server status during data migration■ About migrating multiple partitions■ About the data migration log■ Cancelling data migration■ Run the data migration scripts■ Import the Platform configuration file (distributed environment on multiple

operating systems with Affinium Manager 7.x only)■ Verify data migration■ About migration results

N250002

Before you migrate dataThis section describes the procedures for migrating your existing data from any 5.1+ to6.x version of Campaign to Campaign. These tasks assume that you have successfullycompleted the installation tasks detailed in the installation documentation, and that youare aware of data migration concepts and prerequisites as described in Overview ofdata migration and Preparing the source and target systems.

In addition, we recommend that you read the following before migrating data:

• All of the topics in this section.

• Topics in the Data Migration Reference chapter that describe the expected resultsfor the types of data you want to migrate.

N260002

About web application server status duringdata migration

Follow these guidelines for the web application servers during data migration:

Version 8.5.0 27

3 - Migrating Data

Source systemThe source system web application server can be in any state (running or shut down)during the data migration process. However, if the source system is running andavailable for use, any changes made by users to source system data during datamigration may not be migrated correctly. Moreover, it is possible that changes made tothe source system may cause data to be migrated in an inconsistent state to the targetsystem. Therefore, the best practice is to shut down the source system web applicationserver and listener to prevent use during data migration. If this practice is not followed,IBM Unica technical support may not be able to properly support the migrated systemwithout starting the data migration process again with a clean target system.

Target systemThe target system web application server must always remain running and its listenershould be stopped. This server provides access to the JDBC database drivers used fordata migration. Also, the Marketing Platform web application must be deployed andactive during data migration, as some of the configuration information from the sourcesystem is stored on the Configuration page in Marketing Platform.

N270002

About migrating multiple partitionsFollow these guidelines for migrating multiple partitions:

• If your source system has multiple partitions, make sure that you have set up thesame number of partitions on the target system.

• For each partition in your environment, run the six scripts in sequence to migratesystem table data and all of the corresponding underlying objects. When you startthe data migration at Stage 1, you must choose an initial partition to migrate. If onlyone partition exists, it is automatically selected.

• You cannot change the name of a partition while migrating data; the partition namemust match on the source and target systems.

• You must complete the data migration for each partition before beginning theprocess for another partition; you cannot resume an incomplete data migration afteryou have switched to a new partition.

N280002

About the data migration logAfter you run each data migration stage, the scripts write processing details, warnings,or errors to a log file named migration.log. You set the log’s location and level ofverbosity in the setenv script file, as specified in Set environment variables. When astage completes, it displays the location of the log file.


Cancelling data migration

Details from each stage are appended to the log after the details for the previous stage.If you prefer that details for each data migration stage are captured in a separate file,rename the log file with a different name after each stage completes, so that loggingdetails from the next data migration stage you run are captured in a new log file withoutthe details from the previous stage.

For example, after you run Stage 1, rename migration.log to stage1.log. Loggingdetails for Stage 2 will be written to migration.log.

N290002

Cancelling data migrationYou can abort the data migration at any prompt during any stage by typing abort.

N2A0002

Run the data migration scriptsRun the data migration scripts to migrate Campaign data and files to the target system.

The data migration scripts are located in the tools/migration/5.1+To8.5 directoryin the path where you have installed the data migration tools on the target system. Thescript files are named for the stage they execute, as follows:

• stage1

• stage2

• stage3

• stage4

• stage5

• stage6

The scripts prompt you to provide passwords for your web application server or JDBCdatabase login for the target system. Passwords are not saved by data migrationscripts.

N2E0002

Guidelines for running the data migration scriptsThe following guidelines apply to all of the data migration scripts:

• The data migration scripts create files that are required for the migration to executecorrectly. These files are located in the same directory that you specified for themigration.log file using the LOG_TEMP_DIR parameter. Do not delete any of thefiles in this directory during the migration process.

• UNIX only: Run the data migration scripts as root to ensure access to files withmultiple levels of ownership or permissions.

• UNIX only: Verify that the path to the shell specified at the start of each datamigration script is correct for your system. If it is not correct, modify it before runningthe script.

Version 8.5.0 29

3 - Migrating Data

• After running any of the data migration stages, we recommend that you check themigration.log file for errors, even if no errors are reported.

• If any errors are reported, correct the errors and re-run the script.N2F0002

Stage 1 – SetupThe stage1 script performs the following actions:

• Gathers information about the source and target system

• Sets up database connections to the source and the target system

• Creates or updates temporary migration tables in the target system

Guidelines for running Stage 1Run the stage1 script only once for each partition that you are migrating. However, ifthe script fails to complete, you must run it again.

After Stage 1 of the data migration is complete, do not change any MarketingPlatform user names or Campaign system table mappings. Any users that areadded to Marketing Platform after you run Stage 1 will not be known to the datamigration scripts in any later stage. Stage 1 constructs an internal mapping of usernames to user IDs, which is then referenced by all later data migration stages. Newusers added after running Stage 1 may cause errors in data migration, for example,if objects owned by a new user are migrated during later stages.

Information required for Stage 1This section describes the information that the stage1 script prompts you to provide. Inmost cases, the script attempts to detect the information, and either presents options foryou to select or, if it cannot find the infomation, prompts you to provide it.

Information required Description

Root installation directory of The root installation directory of the target system (PLAT-target system FORM_HOME ). The script provides a default based on the value

of PLATFORM_HOME you set in the setenv script.

Partition details Partition — The script attempts to detect the partitions in thesource Campaign system. If only one partition is defined, it isautomatically selected for data migration. If more than onepartition is defined, you must choose an initial partition tomigrate.

Security policy for PolicyID fields

Default user name for CreateBy fields

Date for CreateDate fields


Run the data migration scripts


Connection details to source The script prompts you to select a connection method to thesystem tables database system tables in both the source and target systems.

If you use WebLogic as the web application server, you canselect WebLogic or JDBC. If you use WebSphere as the webapplication server, you must select JDBC.

Select one of the options:

WebLogic — If you select this option, the script prompts youto enter the following details:

• Host name — for example, mymachine• Port number — for example, 7001• Web application server username and password• Full path (including filename) to the Web application

server’s library .jar file — for example:C:\bea\weblogic81\server\lib\weblogic.jar

JDBC — If you select this option, the script prompts you toenter the following details:

• Driver class name — for example,oracle.jdbc.driver.OracleDriver

• URL including host, database name, and port — forexample,jdbc:oracle:thin:@machinename:1521:orcl

• Database username and password

Source system tables informa- Catalog/database (depending on your database system’s ter-tion minology) — the script detects the available options for you to

select.

Schema/owner (depending on your database system’s termi-nology) — the script detects the available options for you toselect.

Target system tables informa- Catalog/database (depending on your database system’s ter-tion minology) — the script detects the available options for you to

select.

Schema/owner (depending on your database system’s termi-nology) — the script detects the available options for you toselect.

Configuration file directory on The full path to the directory containing thethe source system affinium_config.xml file on the source system. Do not

include the file name. For example,

C:\Affinium\authorization\confdata

Version 8.5.0 31

3 - Migrating Data


Campaign installation directo- The path to the Campaign installation directory on the sourcery on the source system system. For example, C:\Affinium\Campaign

Partition’s parent directory on The path to the selected partition’s parent directory on thethe source system source system. For example,

C:\Affinium\Campaign\partitions

Database ID limits for the Enter new values or change existing values for lower andsource and target systems upper ID limits in your source system.

If during data migration you define ID range values that aredifferent from existing values in the source system’s configura-tion, you must manually update your source system’s configu-ration to correspond with the new ID range values youspecified during data migration. Otherwise, if the sourcesystem remains in production, new objects created there mightbe assigned IDs that fall outside the specified range, and mightnot be migrated by the data migration process. The datamigration scripts do not automatically modify any source dataor files, including configuration files.

For instructions on setting database ID limits, see Set data-base ID limits.

N300002

Stage 2 – Consistency checksThe stage2 script performs the following actions:

• Performs database and file system consistency checks on the source system andreports errors.

• Validates internal ID ranges on both the source and the target system. IDs from thesource system are copied over directly, and the data migration also creates somenew objects requiring IDs. For that reason, the ID range for both systems must notoverlap. For details, see Set database ID limits.

• Checks if the AssignOffer macro exists in any stored derived fields. Fields thatuse this macro cannot be migrated (the AssignOffer macro is no longersupported).

• Identifies whether the audience levels from the source have also been created andmapped on the target, including the same fields and data types.

• Identifies whether there is more than one row in contact or response history havingthe same combinatioin of CustomerID, OfferTrackID, and ContactDate.Redundant rows must be removed from such the contact and response historytables.



• Identifies whether the source system has contact and response history recordspopulated from session flowcharts. Session flowcharts must be removed beforemigrating data.

• Identifies whether the target system is empty (clean).

Guidelines for running Stage 2Follow these guidelines for running Stage 2:

• Stage 2 can be run multiple times for the same partition, but not after Stages 3 or 4have run. Running Stage 2 after Stage 3 or Stage 4 will cause the Clean TargetChecks task to fail. If you need to run Stage 2 multiple times, you must run it afterStage 1 and before Stage 3. Alternatively, you can run Stage 2 from within Stage 5,but you cannot run Stage 2 explicitly after you have run Stage 3 or Stage 4.

• You may need to make adjustments to your source database system or file systemto correct any dependency violations or other errors noted in the log after each runof Stage 2.

N310002

Stage 3 – File system artifactsThe stage3 script performs the following actions:

• Copies artifacts on the source file system to the target system.

• Copies configuration settings from the following files to the Configuration page onthe target system:

• affinium_config.xml

• dbconfig.lis

• unica_aclnsr.cfg

• unica_acsvr.cfg

The following files from pre 6.4.x versions of Campaign are not migrated:

• udisvr.cfg

• Campaign_config.xml

The stage3 script does not migrate any folders other than those originally installedby a Campaign installation in <CAMPAIGN_HOME>/partitions/partition[n].

Prerequisites for Stage 3Ensure that the following prerequisites are met before you run the stage3 script:

• The target server partition must be free of any Campaign objects (for example,folders, campaigns, or offers) before you run the stage3 script. If any Campaigndata exists in the partition, remove it before running the stage3 script.

Version 8.5.0 33

3 - Migrating Data

• In the dbconfig.lis file on the source system, remove any entries for databasesthat are not supported by Campaign, or for which there are no database templateson the target system. These entries will cause Stage 3 to fail if they are notremoved. (If you are migrating from version 5.2.1, you must remove the entry forRedbrick.) The data source templates on the target system are located in the<CAMPAIGN_HOME>/conf directory.

Guidelines for running Stage 3Run the stage3 script only once for each partition that you are migrating. However, ifthe script fails to complete, you must initiate it again. Manual intervention might berequired before you can re-run this script successfully after a failure.

Information required for Stage 3The stage3 script prompts you for the following information:

• Passwords for your web application server or JDBC database login for the targetsystem. Passwords are not saved by data migration scripts.

• Name of the source version’s system tables data source (for example,AC_SYSTEM_TABLE ).

N320002

Stage 4 – Database artifactsThe stage4 script performs the following actions:

• Migrates data that is not associated with a specific campaign or session from thesource system table database into the target system database.

• Migrates as a whole all stored objects referenced by flowcharts in campaigns(custom macros, triggers, and stored derived fields) from the source system to thetarget system. These objects cannot be individually specified for data migration.

Guidelines for running Stage 4Run the stage4 script only once for each partition that you are migrating. However, ifthe script fails to complete, you must initiate it again. Manual intervention might berequired before you can re-run this script successfully after a failure.

If you create any new custom macros, triggers or derived fields after you run thestage4 script, you must manually recreate these objects in the target system.

N330002

Stage 5 – Offer, campaign, and session artifactsThe stage5 script performs the following actions:

• Migrates any campaigns or sessions that you specify, including their associatedoffers.



• Allows you to choose whether to migrate the associated contact history andresponse history data for campaigns.

• Allows you to select, for the item type selected, whether you migrate:

• Individual items — the script prompts you to enter the item name if you choosethis option.

• A folder of items — the script prompts you to enter the folder name if youchoose this option. All contents of its subfolders are also migrated.

• All available items of this type

• Allows you to specify an individual flowchart to re-migrate.

Prerequisites for Stage 5Ensure that the following prerequisites are met before you run the stage5 script.

• If you choose to migrate the contact history and response history data, ensure thatyou have created and mapped all audience level tables in both the source andtarget systems.

• If any of the flowcharts you are migrating has flat files as a data source, the flat filesmust be manually copied from the source system to the target system in theappropriate corresponding location.

• Before migrating sessions, remove all contact processes from session flowcharts.

• Make sure that contact history or response history tables from your source systemdo not contain multiple records with the same customer, date, and offer. For moreinformation, see Contact and response history.

• Make sure that the default audience level Customer is mapped in the target system,even if the Customer audience level is not used in the source system.

• The stage5 script does not verify that campaign and flowchart names contain onlylegal characters. Prior to version 6.2.x, Affinium Campaign allowed campaign andflowchart names to contain some characters that are now restricted. See the IBMUnica Campaign User’s Guide for details about special characters and ensure thatcampaign and flowchart names contain only legal characters before migrating theseobjects.

Guidelines for running Stage 5Follow these guidelines for running the stage5 script:

• Stage 5 can be run multiple times for the same partition to re-migrate objects or tomigrate new objects.

• Each time this script finishes migrating a selected item or group of items, you canchoose whether to migrate more data. You can repeat the data migration stepswithin the script for all items that you want to migrate, before the script completes.

Version 8.5.0 35

3 - Migrating Data

• Migrating contact and response history may take a long time depending on theamount of data to be migrated. You may want to migrate the campaign and itsflowcharts without contact history first and subsequently migrate just the contact andresponse history.

Information required for Stage 5The stage5 script prompts you for the following information:

• Passwords for your web application server or JDBC database login for the targetsystem. Passwords are not saved by data migration scripts.

• For migrating contact or response history data — a user name with administrativeprivileges in Campaign. If you are running the stage5 script for multiple partitions,make sure that you enter a user name that has administrative privileges for thepartition you are currently migrating.

N350002

Stage 6 – Finish data migrationThe stage6 script cleans up and removes temporary data migration tables from thetarget system.

When you run Stage 6, temporary tables created during data migration are deleted.Therefore, you cannot perform further data migration on the same partition afterrunning Stage 6. To perform a new cycle of data migration, you must start againfrom Stage 1, on a clean installation of Campaign.

Prerequisites for Stage 6Run Stage 6 only if you are completely finished with all data migration and re-migrationfor the current partition and no longer need any of the partition’s content from thesource system.

If any of the campaigns or sessions fail to migrate in Stage 5, the stage6 script willfail to execute. If you want to execute Stage 6 without taking further action on anyfailed campaigns or sessions, change the status of taskid 501 in theMigConfig_Status table from 0 to 1.

N2B0002


Import the Platform configuration file (distributed environment on multiple operating systems with AffiniumManager 7.x only)

Import the Platform configuration file(distributed environment on multipleoperating systems with Affinium Manager7.x only)

After completing data migration, if your Campaign web application, Campaign analyticalserver, and the Marketing Platform are installed on different operating systems (forexample, web application and Marketing Platform on Windows and Campaign analyticalserver on UNIX), and your source system has been upgraded to Affinium Manager 7.x,use the Marketing Platform configTool utility to import the Manager_config.xml

file that you exported before performing data migration.

For information on using the configTool utility, see the IBM Unica Marketing PlatformAdminstrator's Guide.

N2C0002

Verify data migrationAfter executing the six data migration stages, verify that the data migration wascompleted successfully.

1. Restart the Campaign server(s).

2. Log in to the target installation of Campaign and verify that you can perform thefollowing tasks:

• View and open flowcharts and process boxes

• Test run flowchartsN2D0002

About migration resultsMost of the objects that you migrate to Campaign successfully do not require furtheraction to complete migration. However, you should be aware of the exceptions listed inthe following topics.

For more information about migrating these and other Campaign objects, see DataMigration Reference.

Objects that may require manual steps tocomplete migration• Control groups

• Dimension hierarchy tables

• Flowcharts that create cubes or strategic segments

Version 8.5.0 37

3 - Migrating Data

• Files or scripts invoked by triggers

• The following processes:

• Contact

• Create Seg

• Optimize

• Response

• Snapshot

• Track

• Any process that uses the AssignOffer () macro

Processes that are migrated but not supportedThe following processes are migrated as part of flowcharts in which they exist, but areno longer supported in Campaign. You must manually delete these processes fromflowcharts before they can be run successfully in the new version of Campaign.

• Decision

• eMessage

• EventIn

• EventOut

• Recommend

Processes that are not migrated or supported• Evaluate

• SelectOpt

• TestOpt

Configuration settings files from pre-6.4.xversions of Campaign that are not migrated• Campaign_config.xml


N10138

4 Data MigrationReference

■ Introduction■ Campaigns■ Cells■ Configuration settings■ Contact and response history■ Control groups■ Cubes and strategic segments■ Custom attributes■ Custom macros■ Derived fields■ Dimension hierarchies■ Flowcharts■ Flowchart templates■ Folders■ Initiatives■ Offers■ Offer templates■ Offer versions■ Processes■ Security■ Sessions■ Table catalogs■ Triggers

N100002

IntroductionThis section provides details about the requirements and limitations for migratingspecific types of data in Campaign, including object types, files, and configurationsettings. Before migrating data from your source system to the target system, refer tothe topics in this section to gain an understanding of the expected results for the type ofdata that you want to migrate.

N360002

Version 8.5.0 39

4 - Data Migration Reference

CampaignsMigrationCampaigns can be migrated individually or as part of a specified folder. Associatedoffers and flowcharts are migrated as part of each campaign. When you migrate acampaign, you can choose to include the associated contact and response history, oryou can migrate the contact and response history at a later time. For details, seeContact and response history.

Re-migrationCampaigns can be re-migrated individually or as part of a specified folder. Associatedoffers and flowcharts are re-migrated as part of the campaign. Flowcharts and offerscan be re-migrated as well.

When you re-migrate campaigns, you can specify how objects already in the targetsystem are handled by choosing either Overwrite or Skip mode. Campaigns that arere-migrated into an existing folder ignore any specified security policy during migrationand use the security policy of the destination folder specified in the target system.

Any new flowcharts in the target system that do not exist in the source system are notaffected or changed when the campaign is re-migrated.

N370002

CellsCells are migrated and re-migrated with processes in flowcharts. For details, seeProcesses.

N380002

Configuration settingsMigrationSettings from the following configuration files are migrated to the Configuration page inMarketing Platform:

• affinium_config.xml

• dbconfig.lis

• unica_aclnsr.cfg

• unica_acsvr.cfg

The following files from pre 6.4.x versions of Campaign are not migrated:

• udisvr.cfg

• Campaign_config.xml


Contact and response history

Re-migrationConfiguration files cannot be re-migrated.

N340002

Contact and response historyMigrationYou can select whether to migrate contact history and response history when you selectcampaigns for migration. You can only migrate both contact history and responsehistory together; you cannot migrate only one and not the other.

You should be aware of the following limitations when migrating contact and responsehistory:

• Sessions — IBM Unica Campaign does not allow migration or re-migration ofcontact or response history records from sessions. Before migrating or re-migratingsessions to Campaign, you must remove any contact processes from sessionflowcharts.

• Date and time fields — Contact and response history records in Campaign nowcontain both date and time fields; contact and response history records from pre-7.xversions of Campaign contain the date but not the time. The combination of offer,date, and customer must be unique for each of these records in Campaign. If thecontact history or response history tables from your source system contain multiplerecords with the same customer, date and offer, data migration will fail and thestage2 script will detect the condition and flag it as an error.

To work around this issue, choose one of the following options:

• Clean up the contact history records by deleting redundant entries.

• Create a view on contact history where rows are normalized by audience key(s),offer, and date. Map this view as the contact history system table.

• Inferred response history records — The data migration script cannot determinewhether a migrated response was direct or inferred, so by default all of theserecords are migrated as direct responses.

As an alternative, you can set all migrated records to be inferred instead of direct.To do this, after migrating response history records, update response records toinferred by changing the value of the DirectResponse field in theUA_ResponseHistory table to 0.

Re-migrationThe following requirements and limitations apply to re-migrating contact and responsehistory:

Version 8.5.0 41


• You can select whether or not to re-migrate contact history and response historywhen you select campaigns for re-migration. You can choose to migrate only thehistory, leaving the campaign (and any subsequent changes that have been madeon the target system) intact. You can only re-migrate both contact history andresponse history together; you cannot re-migrate only one and not the other.

• Contact and response history records that were generated on the same date asrecords already in the target system tables cannot be re-migrated.

• When re-migrating contact and response history, the data migration script checkscontact and response history records on the target system based on date. Recordsfrom the source system that do not have the same dates as records in the targetsystem are inserted into the target system tables. However, if contact and responsehistory records from the source system share dates with records already in thetarget system, these records are not migrated. This situation might arise if flowchartsthat generate contact or response history were run multiple times on the same date.If your source system contains such data, you must remove the redundant recordsfrom the target system before attempting to re-migrate contact and response history.

• If you delete and re-configure a Response process on the source system, theResponseID in the UA_Response table is deleted and a new ResponseID isinserted, corresponding to the same OfferTrackID. Any response history recordscorresponsing to the deleted ResponseID are now "orphaned" (that is, they haveno associated OfferTrackIDs). If response history records are generated for anew date, the records are inserted for the new ResponseID. The data migrationscript cannot migrate the orphaned response history records; only the responsehistory records corresponding to the new ResponseID are migrated.

• If you make changes to a migrated flowchart in Affinium Campaign 6.x that result inchanges to OfferTrackIDs, the old OfferTrackIDs are deleted and the associatedcontact history records are "orphaned" (that is, they have no associatedOfferTrackIDs). If you re-migrate the modified flowchart and contact history, only theOfferTrackIDs and associated contact history records from the current configurationare migrated. Any orphaned contact history records are not migrated.

• To re-migrate the contact and response history, you must also re-migrate themodified flowchart. If you re-migrate only the contact and response history withoutre-migrating the flowchart, the contact history will not be migrated.

Re-migrating contact and response history onlyOption 1 of Stage 5 allows you to choose to migrate contact and response history only.This section describes the results of re-migrating only contact and response history dataunder two scenarios.

Scenario 1

1. Migrate a flowchart from the source system to the target system, without contact andresponse history.

2. Run the flowchart on the source system.

3. Modify the flowchart on the target system.


Control groups

4. Re-migrate only the contact and response history from the source system to thetarget system.

Result: The modified flowchart on the target system is unchanged (not overwritten). Allcontact and response history from the source system is moved to the target system. Ifyou then run the modified flowchart on the target system, the new contact and responsehistory data from that flowchart run will be added to the target system and the migratedcontact and response history data on the target system will remain unchanged.

Scenario 2

1. Migrate a flowchart from the source system to the target system, including contactand response history.

2. Re-run the flowchart on the source system.

3. Modify the flowchart on the target system.

4. Re-migrate only the contact and response history from the source system to thetarget system.

Result: The modified flowchart on the target system is unchanged (not overwritten). Allcontact and response history from the source system is moved to the target system,including any updates to individual contact history records that may have been madewith the Track process (for example, changes to contact date). If you then run themodified flowchart on the target system, the new contact and response history datafrom that flowchart run will be added to the target system and the migrated contact andresponse history data on the target system will remain unchanged.

N390002

Control groupsControl groups are not migrated to the Campaign target system due to significantdifferences in control group functionality between the current version of Campaign andearlier versions of Campaign.

In the current version of Campaign, all controls are:

• no-contact controls,

• never output in contact lists, and

• never rolled up in performance reports.

If you have controls in earlier versions of Campaign you must manually re-create themin the target system.

N3A0002

Cubes and strategic segmentsMigrationAlthough flowcharts containing the Cube or Create Seg processes are migrated, theactual underlying cube or strategic segment files are not migrated.

Version 8.5.0 43


You must re-run these flowcharts after migration to re-create the cubes or strategicsegments before the cubes or strategic segments can be used in the target system.

Cubes configured with multiple input segments are not supported in Campaign. If youmigrate a cube with multiple input segments to a Campaign target system, the cube willbe unconfigured on the target system after migration.

In addition, if any of the cubes that you migrate are based on dimension hierarchies thatuse flat files as tables for input, you must move those flat files to the target system andremap them as they were on the source system. If a cube process still fails to run onthe target system after moving and remapping the associated flat files, delete the cubeprocess and create a new one, configuring it exactly the same as the deleted one, andthen run the new cube process.

Re-migrationFlowcharts containing the Cube or Create Seg processes can be re-migrated, but cubeor strategic segment files are not migrated or re-migrated.

N3B0002

Custom attributesMigrationCustom attributes can be migrated only once, in association with the object of whichthey are an attribute.

Checks for these attributes are performed as a part of Stage 2 execution (SpecialChecks Task); if either of these conditions are present, Stage 2 will fail and thecondition will be logged as an error in the migration.log file.

Non-string data type drop-down values

Campaign versions 8.1.x and 8.2.x do not support non-string data type drop-downvalues for campaign or offer custom attributes. If you are migrating from a 6.x version orupgrading from a 7.x version and you have non-string data type drop-down values forcampaign or offer custom attributes, the best option is to remove the sections thatcontain these values from the unica_fldinfo.xml file on your source system beforeupgrade or migration. If you do not remove these values, they are likely to cause errorsafter upgrade or migration.

Custom campaign attributes

You should be aware of the following limitations when migrating custom campaignattributes:


Custom attributes

• Campaign stores custom campaign attribute values for data types such as text,varchar, and string in the StringValue column in the UA_CampAttribute

table. By default, this column is set to varchar(1024). In Affinium Campaignversion 7.5.x and earlier, these attributes are stored in columns of theUA_CampaignExtAttr table. When you migrate custom campaign attributes toCampaign, if your source version of Campaign contains custom attributes withcharacter values that exceed 1024 bytes, you must either modify these attributes orchange the StringValue column in the UA_CampAttribute table in the SQLupgrade script to accommodate your data.

• If any custom campaign attributes on your source system have names that exactlymatch any of the target’s default system-defined fields or the source’s custom offerattributes, you must rename these attributes before you can migrate them to thetarget system.

Custom offer attributes

You should be aware of the following limitations when migrating custom offer attributes:

• The UA_OfferExtAttr table from earlier versions of Campaign no longer exists inthe current versions of IBM Unica Campaign. Contents of UA_OfferExtAttr in thesource system and offer attribute details from the unica_fldinfo.xml file aremigrated to the corresponding new tables in the target system:UA_OfferAttribute , UA_AttributeDef , and UAEnumAttrValues.

• Campaign stores custom offer attribute values for data types such as text,varchar, and string in the StringValue column in the UA_OfferAttribute

table. By default, this column is set to varchar(1024). When you migrate customoffer attributes to Campaign, if your source version of Campaign contains customattributes with character values that exceed 1024 bytes, you must either modifythese attributes or change the StringValue column in the UA_OfferAttribute

table in the SQL upgrade script to accommodate your data.

• If any custom offer attributes on your source system have names that exactly matchany of the target’s system-defined fields or the source’s custom campaign attributes,you must rename these attributes before you can migrate them to the target system.

The default attribute definitions supplied with IBM Unica Campaign should not beedited after data migration, as this may cause errors. For more information ondefault and custom attributes, see the IBM Unica Campaign Administrator’s Guide.

Re-migrationRe-migration is not supported for custom attributes. That is, new custom attributesadded to source system objects that have already been migrated cannot be migratedeven if the main object (for example, a campaign or offer) can be re-migrated.

However, if you change the values of custom offer attributes in the source system thenre-migrate the offers, the new values of the custom offer attributes are carried over tothe target system. Not all offer attribute values can be re-migrated. For details, see theRe-migration section in Offers.

N3C0002

Version 8.5.0 45


Custom macrosMigrationCustom macros and other stored objects referenced by flowcharts in campaigns(triggers and derived fields) are migrated as a whole from the source system duringStage 4; they cannot be individually specified for migration.

In Stage 5, when campaigns are migrated, flowcharts are migrated, including theirreferences to these objects.

AssignOffer macro

The AssignOffer() macro is not supported in Campaign. Stored derived fields thatuse the AssignOffer() macro are not migrated. When any instances of storedderived fields are not migrated for this reason, a warning is logged in the migration loggenerated by the stage2 script.

Re-migrationRe-migration is not supported for custom macros.

N3D0002

Derived fieldsMigrationDerived fields and other stored objects referenced by flowcharts in campaigns (custommacros and triggers) are migrated as a whole from the source system during Stage 4;they cannot be individually specified for migration.


Re-migrationRe-migration is not supported for derived fields.

N3E0002

Dimension hierarchiesMigrationDimension hierarchies can be migrated only once. Dimension hierarchy definitions aremigrated, but the dimension hierarchy tables are not migrated. They must be set up inthe target system after migration.

Re-migrationRe-migration is not supported for dimension hierarchies.


Flowcharts

N3F0002

FlowchartsMigrationFlowcharts are migrated as part of campaigns or sessions. For details, see Campaignsand Sessions.

Some flowcharts may require manual intervention after migration. In addition, somemigrated flowcharts may contain processes from earlier versions of Campaign that areno longer supported. For details, see About migration results.

Re-migrationThe following requirements and limitations apply to re-migrating flowcharts:

• Flowcharts can be re-migrated as part of campaigns or sessions. In addition,specific flowcharts within campaigns can be selected for re-migration without re-migrating all flowcharts in a campaign.

• Any flowchart associated with a campaign will not be re-migrated if the flowchartalready exists in the target system and there are treatments associated with it in thetarget system.

• If the flowchart selected for re-migration is not found in the target system, but thereare treatments associated with it, the existing treatments and any contact andresponse history associated with that flowchart are deleted before migrating theflowchart. This behavior addresses the scenario where a flowchart has been deletedfrom the target system without its history being cleared.

• If ownership of re-migrated flowcharts has changed in the source system sinceprevious migration, the ownership in the target system will be updated to reflect this.

• If the name of a migrated flowchart has changed on the source system or the targetsystem, the flowchart cannot be re-migrated. Do not change the name of a migratedflowchart if you anticipate the need to re-migrate it.

N400002

Flowchart templatesMigrationAll flowchart template files are migrated intact to the target system, but entries in theUA_FlowchartTmpl table are not populated by migration. The target IBM UnicaCampaign system automatically populates the table the first time that stored templatesare pasted in a flowchart in Edit mode after migration.

Re-migrationRe-migration is not supported for flowchart templates.

N410002

Version 8.5.0 47


FoldersMigrationYou can choose to migrate entire folders of objects. The existing tree structure from thesource system is migrated intact.

Re-migrationYou can re-migrate entire folders of objects.

If objects have been moved between folders in the source system after initial migration,when you attempt to re-migrate, supporting files that were previously migrated to thetarget system will remain in their original folder locations. Folders that are re-migratedignore any specified security policy during migration and use the security policyspecified in the target system.

N420002

InitiativesInitiatives can be migrated and re-migrated.

N430002

OffersMigrationOffers can be migrated individually, as part of a folder’s contents, or as part of acampaign (that is, if a campaign references the offer).

You should be aware of the following limitations when migrating offers:

• Offers are not migrated if they have treatments associated with them in the targetsystem. Such offers are skipped by the migration process, but migration continues.

• The Stage 5 menu option “Offers not associated with any campaign” allows you tospecify an individual offer for migration (you must provide the name of the offer andthe offer version, separated by a comma). Only offers that are not associated with acampaign can be migrated using this option.

• Offers migrated from pre-7.x Campaign versions use offer version code formats thatare not compatible with those used in Campaign. These offers cannot be editedunless the offer version codes are regenerated to use the new format.

• Multi-part offer codes that contain more than four parts cannot be migrated. Youmust modify these offers on the source system before you can migrate them to thetarget system.

Creatives


Offer templates

Campaign does not support multiple creatives per offer. If you are migrating offers withmultiple creatives from a pre-7.x version of Campaign, only the first creative for eachoffer is migrated. Creatives other than the first one associated with an offer are dropped.

Custom offer attributes

For details, see the Custom offer attributes section in Custom attributes.

Offer templates

For details, see Offer templates.

Re-migrationRe-migration of offers is supported in Stage 5 migration, either as part of campaign re-migration, or individually selected when not used in campaigns. When you re-migrateoffers, you can specify how objects already in the target system are handled bychoosing either Overwrite or Skip mode. For details, see Re-migration modes.

Offers that are re-migrated into an existing folder ignore any specified security policyduring migration and use the security policy of the destination folder specified in thetarget system.

If an offer that has been used in production in the target system (that is, an offer thathas written out treatments to the target system tables) is re-migrated, the contact historyfor the offer may become invalid on the target system, depending upon the changesthat have been made to the offer attributes on the source system. Before re-migratingan offer, be sure to evaluate the impact of re-migration on contact history.

When you re-migrate an offer, changes made in the source system (since previousmigration) to any of the following offer attributes are not carried over by re-migration:

• Offer version name

• Version code

• Offer code

• Offer group IDN440002

Offer templatesMigrationPre-7.x versions of Campaign do not contain offer templates. When offers are migratedto Unica Campaign from pre-7.x source systems, the migration process creates adefault template. All migrated offers will use this default offer template in the targetsystem.

Re-migrationWhen offers are re-migrated, their offer templates are not changed. The originaltemplate associated with an offer when the offer was first migrated is left unchanged.

N450002

Version 8.5.0 49


Offer versionsMigrationOffer versions from pre-7.x versions of Campaign are migrated to Campaign as newoffers. Contact history that was associated with each offer version is migrated to eachnew offer in the target system.

After migration, the new offer in the target system has the following:

• Offer name — <Offer name> - <offer version name>

• Offer code — <System-generated offer code> - <version code>

• New offer custom attribute — the value of the offer custom attribute is the offerversion code from the source system

• New offer custom attribute — <Offer name> - <group code> where <group

code> is the OfferGroupID in the UA_Offer table.

Re-migrationRe-migration of offer versions is handled in the same way as re-migration of offers. Fordetails, see the Re-migration section in Offers.

N460002

ProcessesMigrationProcesses that were configured in the source system can in most cases be migrated toCampaign as configured processes and should be available for running without manualintervention. Exceptions are noted below.

After migration, some processes may be unconfigured on the target system anddisplay an Invalid cell code format error, even if the cell code format is thesame as the format on the source system. To configure these processes, open theprocess configuration and click the OK button on the General tab. The process boxwill be configured automatically.

Processes that do not require manual intervention

The following processes are configured and can be run after migration without userintervention:

• Audience

• Call List*

• Cube

• Extract

• Merge


Processes

• Mail List*

• Model

• Sample

• Schedule

• Segment

• Select

• Score

*See the exceptions noted in the Migrating Call List and Mail List processes section.

Processes that require manual intervention

The following processes require manual intervention after data migration:

Process Results of migration

Contact Converted to a Mail List process in migrated flowcharts, butmust be manually reconfigured.

Create Seg Migrated but unconfigured after data migration. You mustselect a security policy for the segment being created.

Optimize Migrated but unconfigured after data migration.

Response Migrated but unconfigured after data migration. After datamigration, you must set up valid User Response Types in theUA_UsrResponseType table, then in the Response processconfiguration dialog, select a Response Type Code and, at aminimum, map Treatment Code as a matching field.

Snapshot Files that have been output from Snapshot processes are notmigrated. You must move these files manually to the targetsystem if desired.

Track Migrated but unconfigured after data migration. Contact statusdoes not exist in pre-7.x versions of Campaign. You mustconfigure migrated Track processes to log to contact history,then set a contact status and treatment code for all existinggenerated treatments.

Migrating Call List and Mail List processes

Call List and Mail List processes are configured and can be run after migration withoutuser intervention, with the following exceptions:

Version 8.5.0 51


• Export destinations: Campaign requires contact processes (Call List and Mail List)to have an export destination specified. In Affinium Campaign 6.x, an exportdestination was not required. If you are migrating contact processes from Campaign6.x that do not have export destinations specified, these processes will beunconfigured after migration to Campaign. You can specify an export destination inyour source system before migration, or reconfigure them in Campaign aftermigration.

• Offer version names: Offer version names are not supported in Campaign. If youhave assigned offers containing version names in Call List or Mail List processes inflowcharts on your source system, these processes will become unconfigured whenthey are migrated to Campaign. You must manually reconfigure these processes.

Processes no longer supported

Flowcharts containing the following processes are migrated. However, these processesare not supported in Campaign. These flowcharts may be configured and may execute,but their results may be unpredictable. Therefore, we recommend that you delete themfrom the target system after migration.

• Decision

• eMessage

• EventIn

• EventOut

• Recommend

Legacy processes not migrated

The following processes from Affinium Campaign 4.x are not supported in Campaign.When flowcharts containing these processes are migrated, these processes will notappear in the migrated flowcharts.

• Evaluate

• SelectOpt

• TestOpt

Cell codes

The Cell Code tab in processes from pre-7.x versions of Campaign does not exist inUnica Campaign. The data migration process finds the proper cell code to associatewith the process from the output process that created a target cell. In the rare case thatthere are two or more different cell code values downstream for the same cell, the datamigration process will choose any one of these to use. The details pertaining to the cellcode chosen and the cell code(s) not chosen are captured in the individual flowchart’slog.

Unica Campaign does not allow a cell used as input into multiple contact processes tohave different cell codes. If different cell codes are desired, you must first copy the cell(for example, use a Select process to "select all") and then assign a different cell nameto the copy of the cell when using it in the second contact process.

AssignOffer macro


Security

The AssignOffer() macro from pre-7.x versions of Campaign is not supported inCampaign. Any processes that use the AssignOffer() macro appear unconfiguredafter migration and must be manually reconfigured.

Re-migrationRe-migration of processes is achieved through re-migration of flowcharts. For details,see Flowcharts.

N470002

SecurityMigrationUsers and groups that existed in the source system are preserved and migrated intact.

The default security policy shipped with IBM Unica Campaign is backward-compatiblefor the following roles without manual intervention:

• Read-only

• Read/write

• Read/write/execute

• Administrator

Re-migrationRe-migration is not supported for security data.

N480002

SessionsMigrationSessions can be migrated individually or as part of a specified folder. Associatedflowcharts are migrated as part of each session.

Stored objects

All stored objects referenced by flowcharts in sessions (custom macros, triggers, andstored derived fields) are migrated as a whole from the source system during Stage 4;they cannot be individually specified for migration.

In Stage 5, when sessions are migrated, flowcharts are migrated, including theirreferences to these objects.

Contact processes

Version 8.5.0 53


Campaign does not allow contact processes (Mail List, Call List) to be used inflowcharts associated with sessions. Before migrating sessions to Campaign, you mustremove any contact processes from session flowcharts. Any contact or response historydata generated from these processes will be lost.

Re-migrationThe following requirements and limitations apply to re-migrating sessions:

• Sessions can be re-migrated individually or as part of a specified folder. When asession is re-migrated, any flowcharts in that session are also re-migrated.

• When you re-migrate sessions, you can specify how objects already in the targetsystem are handled by choosing either Overwrite or Skip mode. For details, seeRe-migration modes.

• Any new flowcharts in the target system that do not exist in the source system arenot affected or changed when the session is re-migrated.

N490002

Table catalogsMigrationAll table catalog file system folders are migrated intact to the target system, but entriesin UA_TableCatalog are not populated by migration. The target IBM Unica Campaignsystem automatically populates the table when stored catalogs are first viewed from aflowchart in Edit mode.

Re-migrationRe-migration is not supported for table catalogs.

N4A0002

TriggersMigrationTriggers and other stored objects referenced by flowcharts in campaigns (custommacros and derived fields) are migrated as a whole from the source system duringStage 4; they cannot be individually specified for migration.


References to triggers, which are stored in the UA_Triggerlist system table, aremigrated. However, the files or scripts invoked by triggers are not migrated. These filesare stored in arbitrary locations, and the migration tool does not move these files. Youmust move the files manually to your target system and ensure that the correspondingvalue in UA_TriggerList is updated.


Triggers

When the UA_TriggerList table is migrated with definitions pointing to locations onthe source system, the trigger definitions must be modified to reflect correct triggerdefinition locations in the target system. Alternatively, any trigger executable that wasreferenced on the source system can be copied to a location on the target system, andUA_TriggerList.Definition can be updated to reflect the new location(s).

Re-migrationRe-migration is not supported for triggers.

Version 8.5.0 55

N101C3

5 Troubleshooting

■ Troubleshooting■ Snapshot process that accepts a Score output cell as input appears

unconfigured after it is migrated■ New folders on the source system do not appear on the target system after

data re-migration■ Inferred response history records are migrated as direct responses■ Stage 2 error after re-running Stage 5■ Stage 2 consistency check fails for a campaign or session when the lock file

is missing■ Stage 3 fails to create default offer template■ Stage 5 fails to migrate contact and response history records prior to year

2000■ Error when migrating or re-migrating flowcharts■ AGFs associated with retired features and migrated through a template fail to

run■ Warning when migrating data from Campaign 5.1.1

N4B0002

TroubleshootingRefer to this section for troubleshooting issues with migrating and re-migrating data inCampaign.

N4C0001

Snapshot process that accepts a Scoreoutput cell as input appears unconfiguredafter it is migrated

Problem or error: A Snapshot process that accepts a Score output cell as inputappears unconfigured after it is migrated.

Solution: To work around this issue, perform the following steps:

1. Open the migrated flowchart for editing on the target system.

2. In the Snapshot process configuration, select the input cell from the Score processin the Input drop-down list.


New folders on the source system do not appear on the target system after data re-migration

3. Click OK to save your changes to the Snapshot configuration.N4D0001

New folders on the source system do notappear on the target system after data re-migration

Problem or error: After re-migrating items such as campaigns, sessions, or offers innewly created folders on the source system, the new folders do not appear on the targetsystem.

Solution: To work around this issue, re-start the target server to flush the cache, or waituntil the target server updates its cache. Any new folders and their contents will thenappear on the target server.

N4E0001

Inferred response history records aremigrated as direct responses

Problem or error: Inferred response history records are migrated as direct responses.

Solution: The data migration script cannot determine whether a response tracked in apre-7.x version of Campaign was direct or inferred, so by default all of these records aremigrated as direct responses.

As an alternative, you can set all migrated records to be inferred instead of direct. To dothis, after migrating response history records, update response records to inferred bychanging the value of the DirectResponse field in the UA_ResponseHistory tableto 0.

N4F0001

Stage 2 error after re-running Stage 5Problem or error: After correcting errors reported by Stage 2 (called from within Stage5), the following error is displayed after directly re-running the stage5 script:

"Initial migration stages are not run successfully. Aborting

migration."

Solution: To continue with data migration, perform the following steps:

1. Run the stage2 script (externally, not from within Stage 5).

2. Ensure there are no errors except for the "Clean Target Check Task" of Stage 2(ignore this error). If other errors are reported, correct them and re-run the stage2

script.

Version 8.5.0 57

5 - Troubleshooting

3. To correct the "Clean Target Check Task" error, manually update theMigConfig_Status table and set Status = 1 where StageId = 2 and taskID =

212.

4. Run the stage5 script (do not run Stage 3 or Stage 4).N500001

Stage 2 consistency check fails for acampaign or session when the lock file ismissing

Problem or error: If a campaign or session lock file is missing from thepartition[n]/campaigns or partition[n]/sessions folder, the Stage 2consistency check will fail for the campaign or session, even though it exists on thesource system.

Solution: Run the stage2 script with the -f option to create the lock file. You shouldthen be able to migrate the campaign or session successfully.

N510001

Stage 3 fails to create default offer templateProblem or error: The stage3 script fails to create the default offer template, and anerror appears in the migration log indicating that five or more offer codes are in use.

Solution: Campaign does not support multi-part offer codes that contain more than fourparts. You must modify these offers on the source system before you can migrate themto the target system.

To work around this issue, follow these steps:

1. Modify the offers on your source system so that none contain offer codes with morethan four parts.

For example, on a Campaign 6.2.5 source system, set the UACOfferCodeUsed

property in the unica_acsvr.cfg file to a value less than five. Theunica_acsvr.cfg file is located in the /Campaign/config directory of yourCampaign source system.

2. Run the appropriate DDL scripts for your database type to re-create and re-populatethe Campaign system tables.

3. Remove the temporary migration tables (prefixed with MIG_) from the targetsystem’s database.

4. Delete any files and folders that have been added to the default folders(partitions/<partition_name>/campaigns, partitions/<partition_name>/catalogs, andso on) for the partition on the target system. Do not delete the default folders.

5. Delete the bootstrap_migration.xml file from the location where you arerunning the data migration scripts.


Stage 5 fails to migrate contact and response history records prior to year 2000

6. Restart the target system and verify that it is a clean system.

7. Rerun the data migration stages beginning with Stage 1.N520002

Stage 5 fails to migrate contact andresponse history records prior to year 2000

Problem or error: Stage 5 fails to migrate contact and response history records datedprior to January 1, 2000 and displays an integrity constraints violated

(parent key not found) error.

Solution: By default, the UA_Calendar table contains DateID records beginning with20000101 (corresponding to January 1, 2000). Contact and reponse history recordsprior to January 1, 2000 fail to migrate because their ContactDateTime orResponseDateTime values refer to date IDs that do not exist in the UA_Calendar

table.

To work around this problem, follow these steps to populate the target system'sUA_Calendar table with the required date IDs.

1. Execute the following queries on your source system's database to determine theearliest contact and response history records:

select min(ContactDate) from UA_ContactHistory

select min(ResponseDate) from UA_ResponseHistory

2. Populate the target system's UA_Calendar table with date IDs for the desiredrange of dates. The following example for SQL Server inserts records for January 1,1999 to December 31, 1999. Replace the values in bold to specify the beginningand end dates, respectively.

The following example code is from the ac_populate_tables_sqlsvr.sql

script in the ddl directory under your Campaign installation. If your database isDB2 or Oracle, use the code from the DDL script for your database type(ac_populate_tables_db2.sql for DB2 orac_populate_tables_ora.sql for Oracle).

declare @date_v datetime

set @date_v = '01/01/1999'

set datefirst 7

set dateformat mdy

while @date_v <= '12/31/1999'

begin

insert into UA_Calendar

(Year, FiscalYear, Quarter, FiscalQuarter,

Month,

WeekOfYear,

WeekOfMonth,

DayOfYear, DayOfMonth, DayOfWeek,

ActualDate,

59Version 8.5.0

5 - Troubleshooting

FirstDayOfWeek,

LastDayOfWeek,

DateID) values

(DATEPART(yyyy, @date_v), DATEPART(yyyy, @date_v), DATEPART(q,

@date_v),DATEPART(q, @date_v),

DATEPART(mm, @date_v),

DATEPART(ww, @date_v),

DATEDIFF(dd, DATEADD(dd,-1,DATEADD(ww, DATEDIFF(ww,0,DATEADD(dd,-

(DAY(@date_v)-1),@date_v)), 0)), @date_v)/7 + 1,

DATEPART(dy, @date_v), DATEPART(dd, @date_v), DATEPART(dw, @date_v),

@date_v,

DATEADD(dd, -1, DATEADD(wk, DATEDIFF(wk,0,@date_v), 0)),

DATEADD(dd, 5, DATEADD(wk, DATEDIFF(wk,0,@date_v), 0)),

CAST (CONVERT (varchar(20), @date_v, 112) AS BIGINT))

set @date_v = DATEADD(dd, 1, @date_v)

end

IBM Unica Campaign - Data Migration Guide

N530001

Error when migrating or re-migratingflowcharts

Problem or error: During data migration/re-migration of flowcharts in Stage 5, themigration.log file may display an error such as the following:

"ERROR stage5.....No resource is associated with key "<KeyName>"

or

ERROR stage5.Stage5Driver [2988] - Unable to get ID table for

identifier null or No resource associated with key....

Solution: You can ignore these errors. They have no adverse effect on the datamigration process or on migrated objects.

N540001

AGFs associated with retired features andmigrated through a template fail to run

Problem or error: If any Affinium Generated Fields (Campaign Generated Fields inCampaign) associated with features that have been retired in Campaign are used in amigrated template, the template will not run successfully.

60

Warning when migrating data from Campaign 5.1.1

Solution: The references to the AGFs in the template will continue to exist in the newenvironment, but must be modified to reference current objects for the templates to runsuccessfully. For example, if tracking codes from Affinium Campaign 6.x are referencedin a derived field calculation, then that derived field must be modified to use Campaign’snew treatment code, or modified in some other way to remove the reference to obsoletetracking codes. Likewise, if the tracking code or any other retired AGF is mapped to anoutput field for a vendor file or to contact history, the retired AGF must be removed andreplaced with a different field before the template can run successfully.

N550001

Warning when migrating data fromCampaign 5.1.1

Problem or error: After running the stage2 script for migrating data from AffiniumCampaign 5.1.1, the migration.log file displays the following warning:

warning: Failed to find the table mapping for UA_IDSByType. It also

displays: templatetablename <---> templatetblname...Fail.

Solution: You can ignore this warning.

Version 8.5.0 61

N10206

A Customizing DataMigration

■ About customizing data migration■ Example custom data migration tasks■ Implementing a custom task■ Removing a custom task from a data migration stage■ Running a customized data migration stage script■ Sample Java classes for implementing data migration tasks

N120002

About customizing data migrationFor best results, engage with IBM Unica Consulting Services before performing anydata migration tasks in Campaign.

Campaign allows you to customize the workflow of migration Stages 2–5 by using themigration configuration utility (acMigConfigTool) to add or remove data migrationtasks. Use custom tasks for data migration needs that are not addressed by the defaulttasks in the data migration stages. Use the Java API provided with Campaign toimplement the Java interface for the data migration stage that you want to customize.

N560002

Example custom data migration tasksThe following are examples of tasks that can be added to the data migration workflow inStages 2–5:

• Back up Campaign data and disk artifacts to a different disk location

• Delete temporary files

• Migrate flat-file output, such as a customer contact lists, from flowchart runs

• Migrate supporting data from user tables

• Migrate log filesN570002


Implementing a custom task

Implementing a custom taskImplementing a custom data migration task has four major steps:

1. Create the task. Depending upon the task and the needs of your environment, thetask could be implemented, for example, as a shell script, SQL script, or a .bat file.

2. Choose a Java class to implement the Java interface for the data migration stagethat you are customizing. Unica provides a set of sample Java classes for Stages2–5. For details, see Sample Java classes for implementing data migration tasks.

3. Ensure that the environment variables required by the data migration scripts havebeen properly set. See Set environment variables.

4. Run the Campaign migration configuration utility ( acMigConfigTool ) to add thecustom task to the data migration stage. When you run the acMigConfigTool

utility, you pass a command to include your custom task as a parameter to the Javaclass. For details, see To add a custom task to a data migration stage.

N5B0002

To add a custom task to a data migration stageEnsure that the stage1 data migration script has been executed before you runacMigConfigTool. If the stage1 script has not been run, acMigConfigTool willgenerate an error.

Run the migration configuration utility ( acMigConfigTool ) and follow the prompts toadd a custom task to a migration stage.

If the custom task that you are adding has dependencies upon other tasks in themigration stage, ensure that you place the custom task in an appropriate position inthe workflow.

N5C0002

Information required for adding data migrationtasksWhen you choose to add a migration task, the acMigConfigTool utility prompts forthe following information:

• Data migration stage where you want to add the task.

• Position in the stage workflow where you want to insert the new task.

• Descriptive name for the task. Example: “Run shell command during Stage 2”.

• Full path and file name of the .jar file that contains the Java class that you areusing to implement the task.

• Full class name of the Java class.

• Command used to execute your custom task. This command is passed as aparameter to the Java class.

Version 8.5.0 63

A - Customizing Data Migration

N580002

Removing a custom task from a datamigration stage

Ensure that the stage1 data migration script has been executed before you runacMigConfigTool. If the stage1 script has not been run, acMigConfigTool willgenerate an error.

To remove any custom tasks in migration Stages 2–5, run the acMigConfigTool

utility and follow the prompts to specify the task you want to delete.

Removing a default task is not recommended. Running a migration script afterremoving a default task will likely invalidate your migration and may causesignificant problems.

N590002

Running a customized data migration stagescript

After customizing a data migration script, you can run the script following theinstructions in Run the data migration scripts.

N5A0002

Sample Java classes for implementing datamigration tasks

The Campaign installation supplies one sample Java class for each of the customizablemigration stages. These classes implement the Java interfaces that allow you tocustomize the migration stages. Each sample class invokes a system call during themigration stage that executes the custom migration task that you specify.

The samplecallouts.jar file in the /tools/migration/5.1+To8.5 directorycontains the following sample Java classes:

• Stage2ShellTask.java





Documents

Data Migration Guidedoc.unica.com/products/campaign/8_5_0/en_us/IBMUni... · Data re-migration refers to the migration of the same object(s) from the source system to the target system