FOCUS AREAS

Resources for Intelligence Platform Migration

Quick Links

Analysis Report Messages

Migration

Solutions Services DataTier

For information about migration tasks, contact your on-site SAS® support personnel to see the SAS Performance Management Solutions: Migration Guide.

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

Messages

caution The Solutions Role Administrator login user ID was not found. The SAS Deployment Wizard will not be able to update the user ID or password during migration. This will cause configuration failures.
SAS Migration Utility looks for the default Person Name (Solutions Role Administrator) or the default Login UserID (slnadm or domain-name\slnadm). This error indicates that neither of these user IDs exist. Use SAS Management Console in the source environment to determine whether the default User IDs were modified.

caution Table table-name has missing values in the column-name column. Please delete the rows with missing values, or set valid column-name values for those rows, before migrating.
Make the suggested changes, and run SAS Migration Utility again to confirm that the error no longer appears.

caution Table table-name should be empty because the primary keys for this table have changed in Solutions Services 5.1. Please back up table table-name and delete its contents before migrating.
After migration, you can reload the table.

caution The SASSDM database will not be exported, could not find the MySQL credentials file.
The SASSDM database is exported for migration by using the MySQL credentials found in the mysqldbs.properties file. That file was created during the previous deployment's configuration. This message indicates that you might have mistakenly deleted that file.

caution Custom directives will be migrated from subordinate repositories into the Foundation repository.
This is an informational message only. In SAS Management Console in the target SAS deployment, metadata is organized in a Folders tab.

caution Any customizations to templates that are stored in DAV will not be migrated.
If you need help with these customizations, contact your on-site SAS support personnel.

caution Alerts associated to Documents in Document Manager will not be migrated.
Generally, these alerts can safely be discarded.

caution The .sas file associated with a custom stored process is copied into the SMU output by levconfig and can be found here: pathname
The .sas source files for the custom stored processes are located at the indicated pathname, which is a relative pathname in the migration package directory. After migration, you must move the .sas files from the migration package to the destination system's disk drive. If you move the .sas files to a different location on the destination machine than they were on the source machine, you must update the pathname in metadata by using SAS Management Console.

caution Stored Process metadata will be migrated from subordinate repositories into Foundation.
This is an informational message only. In SAS 9.2 and later SAS Management Console, metadata is organized in a Folders tab.

caution Document Manager related metadata will be migrated from subordinate repositories into Foundation.
This is an informational message only. In SAS 9.2 and later SAS Management Console, metadata is organized in a Folders tab.


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.