Below are some frequently asked questions relating to migrating a metadata server-based deployment to SAS 9.4.
Q. Where can I find documentation relating to SAS 9.4 migration?
A. Documentation for SAS 9.4 migration can be found in the SAS® 9.4 Intelligence Platform: Migration Guide.
Q. Does SAS offer consulting services to perform migrations for customers?
A. Yes. If you are interested in having a consultant from SAS perform the migration for you, please contact your Customer Account Executive.
Q. Does SAS Technical Support perform migrations for customers?
A. No. SAS Technical Support can answer your questions about performing a migration and can assist with troubleshooting problems while you perform your migration. If you would like a more hands-on approach from someone at SAS, contact your Customer Account Executive to inquire about SAS consulting services.
Q. What are the requirements for migrating to SAS 9.4?
A. The requirements for migrating to SAS 9.4 can be found in the "High-Level SAS Migration Requirements" section (in Chapter 1) of the SAS 9.4 Intelligence Platform: Migration Guide.
Q. How long will my migration take?
A. The length of time it takes to migrate to SAS 9.4 varies depending on the complexity of your environment. Your deployment architecture, the number of SAS products and solutions that you have, and your business requirements all factor into the length of the migration process. Since migration times can vary, it is difficult to say exactly how long your migration will take. Regardless of the complexity, the methodology for migrating to SAS 9.4 should be the same. Following the methodology outlined in the SAS® 9.4 Intelligence Platform: Migration Guide helps ensure a successful transition to SAS 9.4
Q. I am currently running SAS® 9.1.3. Can I migrate to SAS 9.4?
A. If you are currently running SAS 9.1.3, you cannot migrate directly to SAS 9.4. You must first migrate to SAS 9.2 TS2M3 or to SAS 9.3.
Q. Will I need to schedule downtime to perform the migration?
A. Yes, during the migration process, you should schedule downtime for users relying on the current SAS deployment. By doing so, you ensure that all metadata and physical content stay in sync as the current SAS content is migrated to SAS 9.4. Also, when the migration utility creates the migration package, it actually pauses the metadata server. Any attempts to use your current SAS system during this period will fail.
Q. Can I change the number of machines in my deployment when I migrate to SAS 9.4?
A. No, you must maintain your current number of machines when you migrate to SAS 9.4.
Q. Can I change my operating system family when I migrate to SAS 9.4?
A. No. Your SAS 9.4 components must run in the same operating system family as they did in your earlier SAS version. You can migrate within the Windows family (for example, Windows 32-bit to Windows 64-bit) or migrate within the UNIX family (for example, Solaris to HP-UX). You cannot migrate from Windows to UNIX or UNIX to Windows.
Q. Where can I find documentation relating to the SAS Migration Utility?
A. Documentation for the SAS Migration Utility can be found in the SAS Migration Utility Reference section of the SAS 9.4 Intelligence Platform: Migration Guide.
Q. I am planning to upgrade to SAS 9.4 and I do not have a metadata server. I have only SAS Foundation products. Do I need to run the SAS Migration Utility?
A. No, the SAS Migration Utility is not required when upgrading a system with only SAS® Foundation. For environments that do not require migrating a metadata server, see the Migration Planning Worksheet
Q. Where do I get the SAS Migration Utility?
A. The SAS Migration Utility resides in the \utilities folder of the SAS Software Depot. The version of the SAS Migration Utility that you use is determined by the version of SAS that you currently have. For example:
Q. I downloaded the SAS Migration Utility from support.sas.com. Can I use that when I create my migration package?
A. No. The SAS Migration Utility that is available for download on support.sas.com was made available for customers who have not yet received their new SAS software and are interested in assessing the scope of migration of their existing SAS 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.
Q. How do I run the SAS Migration Utility?
A. The SAS Migration Utility must be run from the command line. For Windows users, even though the SAS Migration Utility is an executable file, you must run it from the Windows command prompt. See the "SAS Migration Utility Reference" section of the SAS 9.4 Intelligence Platform: Migration Guide for further instruction.
Q. I am running Windows. Do I run the 32-bit SAS Migration Utility or the 64-bit SAS Migration Utility?
A. You should run the SAS Migration Utility that matches the operating system of the machine that you are migrating. For example, if SAS is currently running on Windows 32-bit, you should run the 32-bit SAS Migration Utility, which contains _32 in the filename. If SAS is currently running Windows x64, you should run the 64-bit SAS Migration Utility, which contains _x64 in the executable name.
Q. Will the SAS Migration Utility install my SAS 9.4 software?
A. No. The SAS Migration Utility is used only to analyze and package your source (current) environment. After analyzing and packaging your source environment with the SAS Migration Utility, you will then use the SAS Deployment Wizard to install and configure your SAS 9.4 software. The SAS Deployment Wizard prompts you for the location of your migration package that you created with the SAS Migration Utility and the SAS Deployment Wizard populates your SAS 9.4 deployment with the content from your previous release.
Q. What logs can be used to troubleshoot problems with the SAS Migration Utility?
A. You can use migrate.log to troubleshoot problems that might have occurred while the SAS Migration Utility was running. The migrate.log is located in your migration package (output directory). It is important to review the migrate.log after running the SAS Migration Utility. Keywords to search for include ERROR, SEVERE, FATAL.
Q. How can I validate that my migration package is valid?
A. First, search your migrate.log for key words such as ERROR, SEVERE, FATAL. Next, review the Analysis Report. The Analysis Report is located in the \AnalysisReport subdirectory underneath your output directory and it can be viewed by opening AnalysisReport.xml with a web browser. This file lists all the products that are configured in your current SAS deployment. It also helps you determine whether updates must be applied to your current SAS products in order to be eligible for automatic migration with the SAS Deployment Wizard. The Analysis Report also reports any errors or warnings that were received during packaging. To understand how to handle these errors or warnings, see SAS Migration Utility: Analysis Report Messages.
|Product Family||Product||System||SAS Release|
|SAS System||N/A||Windows 7 Professional x64||9.4 TS1M0|
|Windows 7 Enterprise x64||9.4 TS1M0|
|Microsoft Windows Server 2012 Std||9.4 TS1M0|
|Microsoft Windows Server 2012 Datacenter||9.4 TS1M0|
|Microsoft Windows Server 2008 for x64||9.4 TS1M0|
|Microsoft Windows Server 2008 R2||9.4 TS1M0|
|Microsoft Windows 8 Pro x64||9.4 TS1M0|
|Microsoft Windows 8 Pro 32-bit||9.4 TS1M0|
|Microsoft Windows 8 Enterprise x64||9.4 TS1M0|
|Microsoft Windows 8 Enterprise 32-bit||9.4 TS1M0|
|Microsoft® Windows® for x64||9.4 TS1M0|
|Microsoft® Windows® for 64-Bit Itanium-based Systems||9.4 TS1M0|
|Apple Mobile Operating System||9.4 TS1M0|
|64-bit Enabled AIX||9.4 TS1M0|
|64-bit Enabled HP-UX||9.4 TS1M0|
|64-bit Enabled Solaris||9.4 TS1M0|
|HP-UX IPF||9.4 TS1M0|
|Linux for x64||9.4 TS1M0|
|Solaris for x64||9.4 TS1M0|
|Date Modified:||2015-03-09 14:58:28|
|Date Created:||2013-06-27 14:11:53|