Problem Note 64015: A memory leak occurs after multiple CONNECT and DISCONNECT statements when you use the SQL procedure with explicit pass-through
When you use the PROC SQL explicit pass-through with a continuous connect and disconnect cycle to a database, SAS might increase memory allocation.
You encounter this issue when you run code similar to the following:
proc sql;
connect to oracle(user=test pw=test path=test);
disconnect from oracle;
connect to oracle(user=test pw=test path=test);
disconnect from oracle;
connect to oracle(user=test pw=test path=test);
disconnect from oracle;
..........
quit;
This memory leak could eventually degrade server performance due to excessive resource usage.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | Base SAS | z/OS | 9.4_M5 | | 9.4 TS1M5 | |
z/OS 64-bit | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft® Windows® for x64 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise 32-bit | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8 Enterprise x64 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro 32-bit | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8 Pro x64 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Enterprise x64 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro 32-bit | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 8.1 Pro x64 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows 10 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 R2 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2008 for x64 | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Datacenter | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Datacenter | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 R2 Std | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2012 Std | 9.4_M5 | | 9.4 TS1M5 | |
Microsoft Windows Server 2016 | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Enterprise 32 bit | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Enterprise x64 | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Home Premium 32 bit | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Home Premium x64 | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Professional 32 bit | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Professional x64 | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Ultimate 32 bit | 9.4_M5 | | 9.4 TS1M5 | |
Windows 7 Ultimate x64 | 9.4_M5 | | 9.4 TS1M5 | |
64-bit Enabled AIX | 9.4_M5 | | 9.4 TS1M5 | |
64-bit Enabled Solaris | 9.4_M5 | | 9.4 TS1M5 | |
HP-UX IPF | 9.4_M5 | | 9.4 TS1M5 | |
Linux for x64 | 9.4_M5 | | 9.4 TS1M5 | |
Solaris for x64 | 9.4_M5 | | 9.4 TS1M5 | |
*
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.
You might experience excessive memory consumption when you have multiple CONNECT and DISCONNECT statements and use the SQL procedure with explicit pass-through.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2019-04-15 16:35:14 |
Date Created: | 2019-04-10 03:50:14 |