Problem Note 64673: The SAS® metadata server runs out of system memory and stops responding
The automatically scheduled batch relationship loading and cleanup tools introduced in SAS® 9.4M3 (TS1M3) might cause the metadata server process to consume all available memory and stop responding. This automatic process is scheduled to run hourly by default.
When this issue occurs, the operating system might kill the metadata server process before the system runs out of memory or the metadata server log might contain error messages similar to the following:
2019-08-14T13:55:38,802 ERROR [0009999] 261:sasadm@saspw - Insufficient memory
The metadata server failure can occur randomly and is not linked directly to the time that the relationship loading process runs.
You might also encounter this issue if you use the sas-relationship-loader command described in the Using the Relationship Loader (sas-relationship-loader) section of SAS® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition.
A workaround is to disable automatic batch relationship loading and cleaning described in the Configuring Automatic Relationship Loading and Cleaning section of SAS® 9.4 Intelligence Platform: System Administration Guide, Fourth Edition.
You should consider applying all available hot fixes for all tiers if you encounter these memory issues.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Metadata Server | z/OS | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft® Windows® for x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise 32-bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Pro 32-bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8 Pro x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro 32-bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows 10 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2008 | 9.4_M3 | | 9.4 TS1M3 | |
Microsoft Windows Server 2008 R2 | 9.4_M3 | | 9.4 TS1M3 | |
Microsoft Windows Server 2008 for x64 | 9.4_M3 | | 9.4 TS1M3 | |
Microsoft Windows Server 2012 Datacenter | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Std | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Microsoft Windows Server 2012 Std | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Enterprise 32 bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Enterprise x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Home Premium 32 bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Home Premium x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Professional 32 bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Professional x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Ultimate 32 bit | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Windows 7 Ultimate x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
64-bit Enabled AIX | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
64-bit Enabled Solaris | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
HP-UX IPF | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Linux for x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
Solaris for x64 | 9.4_M3 | 9.4_M6 | 9.4 TS1M3 | 9.4 TS1M6 |
*
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: | high |
Date Modified: | 2019-09-13 15:36:50 |
Date Created: | 2019-08-23 09:58:52 |