By default, SAS^® 9.4 Metadata Server is configured to run a scheduled metadata backup daily at 1:00 AM. The backup that is scheduled for Mondays at 1:00 AM is configured to be a backup with the Reorganize repositories option enabled. This option reclaims unused disk space that is left from previously deleted metadata objects.

If a certain sequence of events occurs before a metadata backup is run with the Reorganize repositories option enabled, then the metadata server's Foundation repository might become damaged. The damage that is described in this note does not occur when you take a metadata backup without Reorganize repositories enabled.

Corruption Problem in the Foundation Repository

This section describes a series of steps that can lead to a damaged Foundation repository.

1. The problem can occur when you do any of the following for a first step:
   • You start the metadata server.
   • You pause and then resume a running metadata server.
   • You run a metadata backup that has the Reorganize repositories option enabled.
2. Attempt to add a new login to a current SAS identity using a user ID that is already configured for an existing SAS identity. For example, assume that a login with user ID sasdemo is already configured for the SAS Demo User in the DefaultAuth domain. If you try to create a new login for any other SAS identity with a user ID of sasdemo, this action results in an error similar to the following being reported in the metadata-server log:
   2015-10-10T13:03:33,621 ERROR [00868154] 277:sasadm@saspw - Cannot associate a Login with UserID SASDEMO to Identity Some Other User because this UserID is already assigned to a Login for Identity SAS Demo User.
   In this example, you cannot create a login with user ID sasdemo for 'Some Other User' because it already exists for 'SAS Demo User.'
3. Create a new, unique login for any current user or create a new user with an associated unique login. The key is to successfully create a new login that does not currently exist for any user in the metadata.

   Note: You can perform this action from any client (including SAS® Management Console) that enables you to update SAS identities or by using the SAS user import macros.

4. At any time later, you run a metadata backup with Reorganize repositories enabled. This action results in the following messages being logged to the metadata-server log:
   2015-10-12T01:00:00,038 WARN [02031433] :sas - The ID registry appears to be out of sync with the current ID cache contents. Used IDs (209) don't match expected (-791) during reclaim. 2015-10-12T01:00:00,315 WARN [00000004] :sas - ClassId, C0, is not registered in IDGROUP but is used in ID,A4ZVITSR.C0000058, for data set, I0000024.LOCATION. Metadatafiles Repair Recommended. 2015-10-12T01:00:00,315 ERROR [02031433] :sas - The location container in the Foundation repository is missing an ID registry entry. 2015-10-12T01:00:00,316 ERROR [02031433] :sas - Repository Foundation is not properly initialized. Look for details earlier in the server log. An administrator should analyze and repair this repository. 2015-10-12T01:00:00,316 WARN [02031433] :sas - The Foundation repository could not be opened. 2015-10-12T01:00:00,316 INFO [00000004] :sas - NOTE: Unable to open I0000025.METAIMDB for update. Index usage statistics will not be updated.
   After this, new connections to the metadata server are rejected and messages like these continue to repeat until the problem is resolved:
   2015-10-12T06:49:09,195 ERROR [02045422] 2093:sastrust@saspw - Repository Foundation is not properly initialized. Look for details earlier in the server log. An administrator should analyze and repair this repository.
   If the metadata server is stopped and then restarted, the following messages might be seen during start-up:
   2015-10-12T10:20:35,395 WARN [00000004] :sas - ClassId, C0, is not registered in IDGROUP but is used in ID, A4ZVITSR.C0000058, for data set, I0000002.LOCATION. Metadatafiles Repair Recommended. 2015-10-12T10:20:35,395 ERROR [00000008] :sas- The location container in the Foundation repository is missing an ID registry entry. 2015-10-12T10:20:35,396 ERROR [00000008] :sas- Repository Foundation is not properly initialized. Look for details earlier in the server log. An administrator should analyze and repair this repository. 2015-10-12T10:20:35,396 WARN [00000008] :sas- The Foundation repository could not be opened. 2015-10-12T10:20:35,396 WARN [00000008] :sas- The server is being switched to an administrator mode because of the errors and warnings noted above.
   After this, new connections to the metadata server are rejected until the problem is resolved.

Workaround

A workaround for the issue is to analyze and repair the metadata upon start-up of the metadata server. This can be done by using the <DEBUG REPAIR_METADATA_FILES="y"/> option described in SAS Note 36575: "New XML tags are available for the omaconfig.xml file to analyze and repair a damaged SAS^® Metadata Repository."

Solution

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Base SAS 9.4_M3 is available at:

A fix for this issue for Base SAS 9.4_M2 is available at: