Problem Note 55131: Migrating from one maintenance release of SAS® 9.4 to another maintenance release of SAS® 9.4 results in a failure of the migration procedure
 |  |  |  |
During a migration from one SAS® 9.4 maintenance release to another maintenance release, it is possible for the migration to fail. The migration fails as a result of the use of non-default directories as the repository storage locations on the file system. The maintenance level of the target system can be the same level or later as that of the source system.
For example, suppose you have a source system that is configured with a directory similar to the following for the metadata repositories:
/usr/local/SAS/Lev1/SASMeta/MetadataServer/my_meta_repository
In this case, the migration might fail because the non-default directory my_meta_repository does not already exist on the target system.
During migration processing in SAS® Deployment Wizard, the following messages are written to the metadatasrv_configureMetadata_time-stamp.log file:
[echo] 2014-05-23 12.33.55: Exit target startMetadataServer.
[antcall] Exiting /install/SASHome/SASFoundation/9.4/misc/base/sasconf/metadatasrv/config/metadatasrv_config.xml.
[echo] [adhocMetadataServerRecovery] metadata host=myhost.mycompany.com
[echo] [adhocMetadataServerRecovery] metadata port=8561
[echo] [adhocMetadataServerRecovery] metadata userid=sas
[echo] [adhocMetadataServerRecovery] metadata backup configuration=
[echo] [adhocMetadataServerRecovery] user specification flag=true
[echo] [adhocMetadataServerRecovery] user specified location=/usr/software
[echo] [adhocMetadataServerRecovery] metadata server backup path=/backup/metadatasrv/2014-05-19T09_17_49-04_00
[echo] [adhocMetadataServerRecovery] user specified debug flag=FALSE
[echo] [adhocMetadataServerRecovery] backup status property=local.metadatasrv.adhoc.backup.access
[echo] [adhocMetadataServerRecovery] recovery status property=local.metadatasrv.adhoc.recovery.status
[AdhocMetadataServerRecovery.groovy] ERROR: Metadata server recovery failed from backup at "/backup/metadatasrv/2014-05-19T09_17_49-04_00".
[AdhocMetadataServerRecovery.groovy] This recovery does not appear to have been performed by this server or the backup used was from another server, its unique identifier (98F12C00-C560-11E3-B154-005056A06896) does not match that of the server (8A2007F1-37E7-834C-982C-5B2FE1D6275F).
[antcall] Exiting /install/SASHome/SASFoundation/9.4/misc/base/sasconf/metadatasrv/config/metadatasrv_config.xml.
BUILD FAILED
/install/SASHome/SASFoundation/9.4/misc/base/sasconf/metadatasrv/config/metadatasrv_config.xml:639: The following error occurred while executing this line:
/install/SASHome/SASFoundation/9.4/misc/base/sasconf/metadatasrv/config/metadatasrv_config.xml:3427: ERROR: Recovery of migrated metadata server failed.
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:541)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
at org.apache.tools.ant.taskdefs.CallTarget.execute(CallTarget.java:105)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:134)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:62)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.GeneratedMethodAccessor29.invoke(Unknown Source)
To work around the issue, make sure that the repository directory is created before you run SAS Deployment Wizard. For example, for the sample directory shown previously, you would need to pre-create that entire directory (including my_meta_repository) on the target system.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Metadata Server | 64-bit Enabled AIX | 9.4 | 9.4_M3 | 9.4 TS1M3 | |
| 64-bit Enabled Solaris | 9.4 | 9.4_M3 | 9.4 TS1M3 | |||
| HP-UX IPF | 9.4 | 9.4_M3 | 9.4 TS1M3 | |||
| Linux for x64 | 9.4 | 9.4_M3 | 9.4 TS1M3 | |||
| Solaris for x64 | 9.4 | 9.4_M3 | 9.4 TS1M3 | |||
When you migrate from one SAS 9.4 maintenance release to another SAS 9.4 maintenance release, the migration might fail if non-default directories are specified for repository locations.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2015-02-26 10:17:01 |
| Date Created: | 2015-02-03 16:49:29 |