I successfully generated the SMU analysis report on the metadata server using the following command:
./launchsmu.sh -analyze -sasconfigdir /proj/sas/config/Lev1 -sasproductdir /proj/sas/programs -outputdir /tmp/smuoutput -metadatahost hostname -metadataport 8561 -user sasadm@saspw -password ******
However, when executing the same command on the middle-tier server, the utility fails to proceed. Could someone advise on what might be missing or misconfigured for the mid-tier execution
Error:
/proj/sas/programs/SASFoundation/9.4/sas -sysin "/tmp/smuoutput/getVersion.sas" -log "/tmp/smuoutput/getVersion.log"
14:34:40,709 [WARN ] com.sas.services.connection (f2,r0) A connection was returned to the factory by the garbage collector (f2,c0)
14:34:41,481 [INFO ] SMU Not metadata tier because server address : hostaname (masked actual hostname)!= this host address: hostname(masked actual hostname)
14:34:41,483 [ERROR ] SMU The migration utility had an error:
14:34:41,483 [ERROR ] SMU The metadata server tier has to be migrated before any other tier.
14:34:41,487 [ERROR ] ERRLOG The migration utility exited with error:
com.sas.apps.migration.smu.FrameworkException: The metadata server tier has to be migrated before any other tier.
at com.sas.apps.migration.smu.Framework.manageOutputDirectory(Framework.java:777)
at com.sas.apps.migration.smu.Main.init(Main.java:116)
at com.sas.apps.migration.smu.Main.main(Main.java:57)
Hi. The SAS Migration Utility is not detecting that the metadata server tier is your SMU package. The package needs to be cumulative, in that the end result should be that the single package contains all tiers.
You either need to copy the metadata SMU package (the entire outputdir) to /tmp/smuoutput on the middle-tier or share /tmp/smuoutput across both machines.
Hi,
Thank you for your prompt response. I had already copied the smuoutput_metadata directory to the mid-tier machine from metadata server under /tmp prior to executing the command. However, I’m still encountering the same error as noted in my earlier communication. Please advise. Thanks!
If your metadata output directory is named smuoutput_metadata and you copied it to /tmp on the middle-tier, then you either need to rename smuoutput_metadata to smuoutput or change the -outputdir option to smuoutput_metadata so that it matches the folder name you copied to the middle tier.
If that doesn't help, can you give me a directly listing of /tmp & /tmp/smuoutput ?
did not work and still same issue.
/tmp:
smuoutput
smuoutput_old
smuoutput_midtier
/tmp/smuoutput:
manifest.properties
metadata.properties --> file was not originally generated; based on ChatGPT's recommendation, an empty placeholder file was manually created.
migration-schemas
metadata@hostname(masked actual hostname)
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.