Migration

SAS® Marketing Optimization

This topic includes messages that are listed inder the headers of SAS Marketing Optimization, SAS Marketing Optimization Client, SAS Marketing Optimization Launcher, SAS Marketing Optimization Mid-Tier, and SAS Marketing Optimization Server.

For any updates or hot fixes that are required before you can migrate, see the baseline requirements topic.

For properties that you can specify for the SAS Migration Utility during analysis and migration, see the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.

Messages

Total-number numeric measure names exceed the 26-character restriction. However, all proposed numeric measure names produced by truncation to 26 characters result in unique names that do not appear as substrings within customer or communication character attributes. The requested automatic re-naming of numeric measure names whose length exceed the 26-character restriction failed. See the analyze_datastore SAS log file in the mktopt analysis_results subdirectory. See the report-name HTML report in the directory-name SMU output subdirectory for a summary of numeric measure names exceeding 26 characters in length.

This error indicates that the property mktopt.numeric.measures.autorename=true and the automatic renaming should have completed successfully, but did not. See the analyze_datastore log for more information. See the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.

Total-number numeric measure names exceed the 26-character restriction. Re-naming of the numeric measure names whose length exceed the 26-character restriction must be performed manually using the SAS Marketing Optimization graphical user interface (GUI) because automatic re-naming was not requested. As an alternative to manually renaming the numeric measure names using the GUI, add the mktopt.numeric.measures.autorename property with a value of true to the SMU.properties file and re-run the SAS Migration Utility. See the report-name HTML report in the directory-name SMU output subdirectory for a summary of numeric measure names exceeding 26 characters in length.

See the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.

Total-number numeric measure names exceed the 26-character restriction. Re-naming of the numeric measure names whose length exceed the 26-character restriction must be performed manually using the SAS Marketing Optimization graphical user interface (GUI) because the proposed numeric measure names produced by truncation to 26 characters results in the following problem(s): Total-number of the proposed numeric measure names would be duplicates when fully qualified by input data, project, and scenario. Total-number of the proposed numeric measure names appear as substrings within one or more communication character attributes. Total-number of the proposed numeric measure names appear as substrings within one or more customer character attributes. See the report-name HTML report in the directory-name SMU output subdirectory for a summary of numeric measure names exceeding 26 characters in length.

You must manually rename the numeric measures that are listed in the HTML report.

The SAS Marketing Optimization Server extension cannot execute because one or more of the following properties have been incorrectly set: mktoptconfig.appserver.context.directory, mktoptconfig.autoexec.directory.and.name.

See the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.

Migration of this SAS environment is not recommended. This version of product-name is not at the required version and needs to be upgraded in order to use the automated migration processes.

A message like this indicates that a product needs an update or hot fix in the previous deployment before you can migrate. See the baseline requirements topic.

There are total-number optimization jobs and total-number refresh jobs scheduled for execution in the SAS 9.1.3 environment. It is recommended that the scheduled execution of these jobs be manually cancelled in the 9.1.3 environment before migration of SAS Marketing Optimization (5.1) is performed. Regardless of whether or not their scheduled execution in SAS 9.1.3 is cancelled, these jobs will not be automatically re-scheduled for execution in the SAS 9.2 environment. They must be manually re-scheduled in the SAS 9.2 environment.

For information about post-migration steps, contact your SAS on-site personnel for the SAS Marketing Optimization Migration Guide.

Data location customizations have resulted in one or more SAS Marketing Optimization (mktopt) data directories existing outside of the LEVCONFIG directory. Each of these directories may need to be manually copied to the SAS 9.2 environment if that environment is on a different machine and if the directory is not network accessible:

This is a post-migration task to be completed in the new environment. The data directories can contain SAS data sets, log files (from optimization executions), xml files (for surfaced reports), and SAS programs (for optimization jobs and OLAP cube generation). If you will be migrating from a 32-bit Windows environment to a 64-bit Windows environment, the following document will explain what additional steps you need to take to perform migration of SAS data sets: Migrating a SAS Deployment to Microsoft Windows for x64 (.pdf).

There are total-number optimization jobs and total-number refresh jobs scheduled for execution in the current SAS environment. It is recommended that the scheduled execution of these jobs be manually cancelled in the current environment before migration of SAS Marketing Optimization Server is performed. Regardless of whether or not their scheduled execution is cancelled, these jobs will not be automatically re-scheduled for execution in the new environment. They must be manually re-scheduled in the new environment.

Although it is not required, it is strongly recommended that you cancel these scheduled jobs. For information about pre- and post-migration steps, contact your SAS on-site personnel for the SAS Marketing Optimization Migration Guide.

One or more SAS Marketing Optimization Server data directories exist in a file system location which is not automatically included in the migration package. If these directories are in the SAS Config Dir/Lev1/Applications/SASMarketingOptimizationDotVer directory or other LEVCONFIG directories, then include the levconfig.user.dirs property in your smu.properties file and set its value to a comma-separated list of these directories per the SAS Migration Utility documentation. Otherwise, each of these directories may need to be manually copied to the new environment if that environment is on a different machine and if the directory is not network accessible.

This message is completed by a list of custom directory file locations that can include one or more of the following: DATASTORE=, PROJECTS=, PUBLISHED_SOLUTIONS=, PROMOTED_SOLUTIONS=, OLAP_CUBES=, MOMA_INPUT_DATA=, MOMA_AGENT_TABLES=. For information about pre- and post-migration steps, contact your SAS on-site personnel for the SAS Marketing Optimization Migration Guide.

Migration of this SAS environment is not recommended. This version of the SAS Migration Utility does not support migration for product-name.

Verify that you are using the SAS Migration Utility that is included in your order. A copy of the SAS Migration Utility is available to download for a preliminary analysis of your previous deployment. When you are ready to proceed with your migration, use the SAS Migration Utility that is included in your order to perform your analysis, assess requirements, and create the migration package. If you use a SAS Migration Utility other than the version included in your order, it might support a different set of products and components than your order, and the migration package could produce inaccurate results.

If your Migration Utility is correct and you still receive this message in any section of the Analysis Report, then you should wait to perform a migration of your deployment until the product is supported.

It is possible to create a migration package, and use that package to deploy the new system without the unsupported product. However, data associated with the unsupported product is not migrated. Later, when the product becomes supported and you want to add the product to your new deployment, you will be required to recreate all content, because you cannot migrate a single product with SAS Migration Utility.

For more information, contact SAS Technical Support.

Contributing to Migration

The migration team appreciates your feedback. Send e-mail to Migration.Feedback@sas.com with questions and comments for our developers, testers, and writers.

E-mail This Page

FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links

Migration

SAS® Marketing Optimization

Messages

E-mail:
Password