• support.sas.com

• Knowledge Base

• Support

• Training & Bookstore

• Community

Resources for Intelligence Platform Migration

• SAS Intelligence Platform: Migration Guide
  
  
• SAS 9.3 Guide to Software Updates
  
• Maintenance Release Announcement for SAS 9.2
  
  
• Special Considerations for Customers Upgrading to SAS 9.2
  
  
• Getting from SAS 9.1.3 to SAS 9.2: Migration Tools or Promotion Tools (.pdf) (SGF 2009)
  
  
• Migrating a SAS Deployment to Microsoft Windows for x64 (.pdf)
  
  
• Peaceful Coexistence: Multiple SAS Releases
  
  
• SAS Notes for metadata-based deployments
  
  
• The Lowdown on the Download: What’s Really in My SAS Software Depot and How Did It Get There? (.pdf) (SGF 2010)

Quick Links

• Install Center
• Section 508 Accessibility
• Expanded Table of Contents
• Contact Us

Analysis Report Messages

Migration

SAS Metadata Server

The SAS® Metadata Server controls access to a central repository of metadata that is shared by all of the applications in the SAS Intelligence Platform.

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

Messages

Unable to locate repository manager.

Verify that the -sasconfigdir parameter on the command line, or the SMU.config.dir property in smu.properties, is correct.

The SAS Migration Utility gathers the subdirectories of the configuration directory (from -sasconfigdir or SMU.config.dir). Progressing through each subdirectory, the SAS Migration Utility looks for one of the following items:

• a next-lower-level subdirectory named "rposmgr"
• a file named "omaconfig.xml".

A next-lower-level subdirectory named rposmgr is assumed to be the repository manager. A file named "omaconfig.xml" is treated as a metadata server configuration file, which is parsed to find the location of the repository manager if the repository manager has not been located.

This message probably indicates that no subdirectory of the configuration directory contains one of these two items that specify a valid repository manager.

Missing repository manager data set(s).

Contact the administrator for your metadata server.

Repository repository-name is missing one or more data set(s).

Contact the administrator for your metadata server.

Multiple repositories of type Foundation are registered for this metadata server.

Consolidate the content of all the Foundation repositories into a single Foundation repository, and then remove the extra Foundation repositories.

No repository of type Foundation is registered for this metadata server.

A valid SAS 9.2 or later metadata server requires one, and only one, Foundation repository to be registered.

The server tier does not exist.

This message appears in the second maintenance release for SAS 9.2 only. In a multi-tiered deployment, this message can appear on any machine. The message indicates that the metadata server context cannot be found on this machine. If the message did not display on the machine that hosts the metadata server tier, then no action is needed, and migration can proceed.

No metadata server was detected in configuration directory your-Levn-directory.

This message indicates that the migration utility did not find the metadata server in the location that you specified in the command line (for example, -sasconfigdir C:\SAS\Config\Lev1 or in SMU.properties (for example, SMU.config.dir=C:\SAS\Config\Lev1).

Use of repository type Custom is preferred over use of repository type Project.

This message indicates that when you migrated from a previous release, you had one or more Project repositories that were reinitialized. Project repositories are not reinitialized in the current migration, and they are ready for use after migration. However, a best practice is to discontinue the use of Project repositories and instead use Custom repositories, which are the currently supported type for non-Foundation repositories.

Unable to locate file file-name.

This is a warning message for omaconfig.xml, adminUsers.txt, or trustedUsers.txt. Determine whether the metadata server should be migrated without the specified file.

An omaconfig.xml file is not required, but its usage is very common. An adminUsers.txt file is almost a requirement, and the absence of the file might be cause for concern. A trustedUsers.txt file is not required, but its usage is also common.

AuthenticationDomain objects exist in repository repository-name. AuthenticationDomain objects will be migrated to the foundation repository.

No action is needed if you want the AuthenticationDomain objects to be located in the Foundation repository in the target SAS deployment.

Located repository repository-name of type Project owned by group owner-name. Group ownership will be disallowed. This repository will be deleted during migration.

The repository and the metadata it contains will be deleted from the target SAS deployment. If you want to migrate the repository, change the ownership so the repository is owned by a non-group Identity.

Located repository repository-name of type Project with no owner. A repository of type Project will be required to have an owner. This repository will be deleted during migration.

The repository and the metadata it contains will be deleted from the target SAS deployment. If you want to migrate the repository, assign an owner Identity.

Located repository repository-name of type Project owned by owner-name.

This message informs you of the ownership of a project repository, to help you determine whether to migrate the metadata. Project repositories will be reinitialized in the target SAS deployment, and the previous deployment's metadata will be deleted. Check in any new or checked-out metadata that you want to migrate.

Metadata is checked out to project repository repository-name.

Project repositories will be reinitialized in the target SAS deployment, and the previous deployment's metadata will be deleted. Check in any metadata that you want to migrate.

New metadata exists in project repository repository-name.

Project repositories will be reinitialized in the target SAS deployment, and the previous deployment's metadata will be deleted. Check in any metadata that you want to migrate.

This repository will be reinitialized during migration. It will appear as a new repository.

Check in any new or checked-out metadata that you want to migrate.

This repository will be deleted during migration.

Check in any new or checked-out metadata that you want to migrate. If the repository is owned by a group, or has no ownership, change the ownership so the repository is owned by a non-group Identity.

The trusted peer list name is not migrated.

The migration utility has located a file (usually named trustedPeers.xml) that contains the trusted peer list. This file is not migrated as a part of the migration process. You must migrate this file manually. See the topic about trusted peer connections in SAS Intelligence Platform: Security Administration Guide.

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.