Problem Note 48880: Stored process execution might fail when referencing promoted metadata libraries
Each metadata library object in SAS® Management Console contains a metadata ID such as AYYYYYYY.AZZZZZZZ. When a metadata library object is promoted from one environment to another using the SAS Management Console promotion tools, the metadata IDs of the original and promoted library content will be different.
When you create stored processes in SAS
® Enterprise Guide
® that reference metadata libraries, the associated META library engine assignment fails with the following error from within the new environment:
ERROR: Cannot retrieve metadata from SAS Metadata Repository.
ERROR: Error in the LIBNAME statement.
ERROR: Libname XX is not assigned.
The SAS Enterprise Guide Stored Process wizard uses the LIBNAME statement's LIBID option to reference the library object in metadata. When the promoted library object ID no longer matches the original value, the library cannot be found.
The following workarounds are available for this issue.
- Instead of promoting metadata content, use migration to move metadata content from one environment to another.
- Modify the stored process LIBNAME statement to use the new LIBID value. (Note: This is not recommended with a large number of stored processes.)
- Re-create the stored process. On the librefs page of the stored process wizard, select Use custom LIBNAME statement. Instead of using the LIBID option, use the LIBRARY=name option (where name specifies the value in the SASLibrary object's name).
For additional information about the metadata LIBNAME, see LIBNAME Statement for the Metadata Engine
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Enterprise Guide | Windows 7 Home Premium x64 | 5.1 | 7.1 | | 9.4 TS1M1 |
Microsoft® Windows® for x64 | 5.1 | 7.1 | | 9.4 TS1M1 |
Microsoft Windows 8 Pro | 5.1 | 7.1 | | 9.4 TS1M1 |
Microsoft Windows Server 2003 Datacenter Edition | 5.1 | | | |
Microsoft Windows Server 2003 Enterprise Edition | 5.1 | | | |
Microsoft Windows Server 2003 Standard Edition | 5.1 | | | |
Microsoft Windows Server 2003 for x64 | 5.1 | | | |
Microsoft Windows Server 2008 | 5.1 | 7.1 | | 9.4 TS1M1 |
Microsoft Windows Server 2008 for x64 | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows 7 Enterprise 32 bit | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows 7 Enterprise x64 | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows 7 Home Premium 32 bit | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows 7 Professional 32 bit | 5.1 | 7.1 | | 9.4 TS1M1 |
Microsoft Windows Server 2012 | 5.1 | 7.1 | | 9.4 TS1M1 |
Microsoft Windows XP Professional | 5.1 | | | |
Windows 7 Professional x64 | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows 7 Ultimate 32 bit | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows 7 Ultimate x64 | 5.1 | 7.1 | | 9.4 TS1M1 |
Windows Vista | 5.1 | | | |
Windows Vista for x64 | 5.1 | | | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2015-03-24 14:57:33 |
Date Created: | 2013-01-09 14:55:12 |