The SAS Metadata Server might become unresponsive because of a memory overlay (segmentation violation). Both existing and new connections to the SAS Metadata Server might be unresponsive. You might also see a segmentation violation in the SAS Metadata Server log.

To recover from the unresponsive state, restart all SAS^® servers in the proper order. It is important that you stop each server process in the normal manner. To stop the processes correctly, see the instructions:

• For SAS^® 9.2, the instructions are documented in "Part 2: Starting, Stopping, and Checking the Status of Servers" in the SAS^® 9.2 Intelligence Platform: System Administration Guide, Second Edition.
• For SAS^® 9.3, the instructions are documented in "Part 2: Starting, Stopping, and Checking the Status of Servers" in the SAS^® 9.3 Intelligence Platform: System Administration Guide, Second Edition.

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 Threaded Kernel Metadata Component 9.3_M2 is available at:

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

A fix for this issue for Threaded Kernel Metadata Component 9.3_M1 is available at: