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
Level Configuration
Level Configuration represents the SAS® application server components of the SAS configuration.
For any updates or hot fixes that are required before you can migrate, see the baseline requirements topic.
Messages
This system
cannot be migrated to SAS 9.2. SAS Foundation must be at service pack 4 or later. This system
is at version-number
- You must upgrade to meet the baseline requirements. Contact SAS and request SAS 9.1.3 SP4, or download it from the support site.
Customizations to the
SAS Application Server autoexec and configuration files are not migrated automatically.
Any customization of these files must be added manually to the new system after the
SAS Deployment Wizard is complete.
- This informational message reminds you that customizations must be manually migrated. You must make similar customizations to the target SAS deployment as were made to the previous deployment.
- Some of the file(s)
or sub directories from Data / environment directory were excluded from migration package.
The details of which are stored in pathname
- This message indicates that files were excluded from migration due to an error such as incorrect permissions. Examine the contents of excludedfiles.log in the specified location. If the listed files are necessary, manually copy them to the target SAS deployment. For example, if the person who is running the migration does not have read permission for a file, then the root user or the file's owner can copy the file with the usual operating system commands.
- The Data Package
"item-name" will not be migrated, as its source directory "item-name" does not reside in
SAS configuration directory.
Any .sas source files in this directory will copied to "pathname" in the migration package for future reference.
- If the target SAS deployment is installing on a different machine from the previous deployment,
manually migrate the data package to the target SAS machine. Alternatively, you can copy .sas files from the
migration package in tier-name/levconfig/datapackagesuffix.
In addition, verify that the pathname is correct in metadata for that data package.
A data package can be a source code repository for stored processes and jobs, a database catalog or schema, or a SAS library. For more information about migrating these items, see the post-migration tasks in SAS Intelligence Platform: Migration Guide.
- The Data Package "item-name"
will not be migrated, as its path "pathname" is not absolute and it is not associated with any of
the server contexts on this machine.
- This message indicates that the data package is not associated with any server context and has relative
path. Manually migrate the data package to the target SAS deployment.
In addition, correct the pathname in metadata for that data package.
A data package can be a source code repository for stored processes and jobs, a database catalog or schema, or a SAS library. For more information about manually migrating these items, see the post-migration tasks in SAS Intelligence Platform: Migration Guide.
- The Data Package "item-name"
having path "pathname" will not be migrated, as its location on the disk could not be determined.
- This message indicates that the pathname specified for the data package does not exist or
it is corrupted. Examine the SAS files at the specified pathname.
If the SAS files are necessary, you can either correct the errors and run SAS Migration Utility again,
or manually migrate the data package to the target SAS deployment.
In addition, correct the pathname in metadata for that data package.
A data package can be a source code repository for stored processes and jobs, a database catalog or schema, or a SAS library. For more information about manually migrating these items, see the post-migration tasks in SAS Intelligence Platform: Migration Guide.
- Item Store files (These files are in the
migration package, But if you are migrating on cross platform/architecture machine the item store files
will not be migrated)
- See more information about different kinds of item stores and migration tasks.
- Errors encountered while running
CPORT on catalogs from pathname directory. Please refer to the log file filename for more details.
- This message indicates that the log file contains one or more error messages that might need your attention.
When you examine the log file, if the log message states that a catalog was created for a different operating system, then you probably moved that catalog from a different deployment without converting it. For example, the ORIONFMT catalog was used for SAS BI Dashboard sample code in a previous release. If you no longer need the BI Dashboard samples, then you can delete the catalog or ignore the error message. Here is more background about the issue: If the CPORT procedure cannot write the catalog to the transport file, then your SAS session was probably also unable to access the catalog. So this message usually indicates that the catalog was not in use. However, you are encouraged to research the possible need for the catalog and keep a copy of the catalog in your backup. For more information about PROC CPORT, see the Base SAS Procedures Guide.
- The Data Package "item-name"
will not be migrated, as its source directory "pathname" is a symbolic link.
- If a data package SAS library path is defined as a symbolic link on UNIX, then it cannot be migrated. The content is not packaged and the path on the target side is not changed.
- Service pack information can not be retrieved.
- This message indicates that an exception or error occurred while the the service pack information was being retrieved. Try running SAS Migration Utility again. If the error continues, contact your on-site SAS support personnel.
Item store files found. If you are migrating
on a cross platform/architecture machine the item store file will not be migrated automatically.
- See more information about different kinds of item stores and migration tasks.
- Service pack information
can not be retrived. SAS Foundation must be at service pack 4 or later to perform migration.
- Verify the SAS version and service pack level by running some SAS code and viewing the SAS log. The service pack level is displayed at the top of the SAS log when you run a job. You must be running SAS 9.1.3 SP4 before you can migrate. If you need to upgrade, contact SAS and request SAS 9.1.3 SP4, or download it from the support site.
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.
