Providing software solutions since 1976
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
Analysis Report Messages
|
Migration
SAS® Grid Manager
These messages are printed in the Analysis Report under the headers "SAS Grid Manager Grid Node" and "SAS Grid Manager Grid Control 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
The logical grid server "server-name"
does not have a host name associated with it. Please add the host name or delete the grid monitoring server
from the metadata.
- Verify that all grid monitoring servers have a host name in their connection, or delete the grid monitoring servers that do not have a hostname in their connection.
- Logical grid servers without a host name
cannot be migrated when the grid monitoring servers reference more than one machine. You can migrate logical
grid servers by specifying their SAS Application Server name(s) on the "SMU.grid.appservers" property.
- This message is applicable in migrations from SAS 9.1.3 only. You must specify which logical grid servers should migrated with this host. Use the SMU.grid.appservers property to specify the names of the SAS application servers that contain the logical grid servers for this grid control server. See the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.
- Unsupported Analyze type
- Migration only supports the full analyze mode. A selective migration is not supported.
- Cannot find the migration extension directory pathname for GRDCCTLSVR/GRDCNODE
- Verify that the migration package directory is specified on the command line or through the SMU.Output.Dir property. See the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.
- Cannot find the SAS configuration directory pathname
- Verify that the correct SAS configuration directory is specified on the command line or through the SMU.config.dir property. See the chapter about product-specific SAS Migration Utility properties in SAS Intelligence Platform: Migration Guide.
- Metadata server is not running.
- Verify that you specified the metadata hostname, port, user, and password correctly.
- Cannot connect to the metadata server
- Verify that you specified the metadata hostname, port, user, and password correctly.
- An exception has occurred accessing metadata information: item-name
- Contact SAS Technical Support.
- An exception has occurred communicating to the metadata server: item-name
- Contact SAS Technical Support.
- A file IO error occurred creating the Execute script item-name
- Verify that you have write permission to the migration package directory.
Grid execution script directory
"pathname" does not have a
corresponding logical grid server and will not be migrated. References to this directory will need to be
manually updated.
- The name of the directory that contains the GridServer subdirectory must match the name of a SAS application server context in metadata. For example, if the GridServer subdirectory is in the SASApp directory, the migration utility searches the metadata for a SAS application server named SASApp. This message indicates that the name of the parent directory to the GridServer subdirectory does not match the name of any SAS application servers defined in the metadata. You can either rename the parent directory or manually migrate the information in the GridServer subdirectory. To manually migrate the information, copy the new sasgrid script file and any other files you created (such as config files) to the new GridServer subdirectory. In addition, update any references to the directory in the metadata.
Backing up grid execution script
directory. NOTE: Options added to the sas command line in the old script will need to be put in the
command field of the Logical Grid Server.
- If you have added SAS command line options to the script file in the GridServer subdirectory, move those options to the end of the logical grid server Command field. Make this change in the target deployment after you migrate.
- Located grid script directory
"pathname" so host is either a grid control server or grid node
- No action is needed. This is an informational message that this machine must be a grid control server or a grid node because a GridServer subdirectory was found in the SAS configuration directory structure. The machine will be migrated as a grid control server if the metadata points to this machine as a grid monitoring server or a logical grid server. If the metadata does not point to this machine, it is assumed to be a grid node.
- Host name matches an existing logical grid server so this host will be migrated as a grid control server
- No action is needed. This is an informational message that this host will be migrated as a grid control server, because one of the logical grid servers reference this machine.
- Since all grid monitoring servers reference this host, all logical grid servers without a host name will be migrated with this machine.
- No action is needed. This is an informational message that this host will be migrated as a grid control server even though none of the logical grid servers reference it, because all grid monitoring servers reference this machine.
- Host name matches an existing grid monitoring server so this host will be migrated as a grid control server
- No action is needed. This is an informational message that this host will be migrated as a grid control server, because a grid monitoring server references this host
- Host host-name is a logical grid server in [pathname]/[pathname]/[pathname]
- No action is needed. This is an informational message that a logical grid server was found whose hostname matches this machine's hostname.
- Host host-name is a grid monitoring server in [pathname]
- No action is needed. This is an informational message that a grid monitoring server was found whose hostname matched this machine's hostname.
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.
