Problem Note 37099: An error occurs when using the synchronization process to add a new metadata identity
When adding new metadata identities to a SAS® Metadata Repository using the programmatic approach of user import and synchronization, the %MDUCHGLB macro might generate messages similar to the following:
ERROR: The symbolic reference for A5NT1OPP.$CN=Davi did not resolve.
ERROR: Errors returned from Proc Metadata prevented objects from being Added, Updated, or
Deleted. Table: work.mduchglb_failedobjs identifies 32 such objects. Consult the SAS Log for
the specific Metadata Server errors returned.
The problem occurs when the synchronization process identifies an identity to add to metadata, and the KEYID value is longer than 7 bytes. This error causes the synchronization process to fail. No updates are made to metadata.
If no identities are identified to be added, then the synchronization process correctly updates existing metadata identities, and deletes identities that are identified for deletion.
As a circumvention, use the %MDUCHGL macro. This macro is the same macro that was used in SAS® 9.1.3. It is still provided and supported in SAS® 9.2 installations. The SAS 9.1.3 macro does not perform block loading, and is somewhat less efficient when there are a lot of metadata changes.
For more information on the %MDUCHGLB macro, see Appendix 2 "User Import Macros" in SAS® 9.2 Intelligence Platform Security Administration Guide.
For more information on the %MDUCHGL macro, see Appendix 2 "Bulk-Load Processes for Identity Management" in SAS® 9.1.3 Intelligence Platform: Security Administration Guide, Second Edition.
Operating System and Release Information
SAS System | Base SAS | z/OS | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows XP 64-bit Edition | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft® Windows® for x64 | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows Server 2003 Standard Edition | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows Server 2008 | 9.2 TS1M0 | 9.2 TS2M3 |
Microsoft Windows XP Professional | 9.2 TS1M0 | 9.2 TS2M3 |
Windows Vista | 9.2 TS1M0 | 9.2 TS2M3 |
64-bit Enabled AIX | 9.2 TS1M0 | 9.2 TS2M3 |
64-bit Enabled HP-UX | 9.2 TS1M0 | 9.2 TS2M3 |
64-bit Enabled Solaris | 9.2 TS1M0 | 9.2 TS2M3 |
HP-UX IPF | 9.2 TS1M0 | 9.2 TS2M3 |
Linux | 9.2 TS1M0 | 9.2 TS2M3 |
Linux for x64 | 9.2 TS1M0 | 9.2 TS2M3 |
OpenVMS on HP Integrity | 9.2 TS1M0 | 9.2 TS2M3 |
Solaris for x64 | 9.2 TS1M0 | 9.2 TS2M3 |
*
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.
The %MDUCHGLB macro generates a message like the following:
ERROR: The symbolic reference for repository_id.$keyid_value did not resolve
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2009-09-24 15:23:49 |
Date Created: | 2009-09-04 13:58:21 |