With SAS/ACCESS Interface to Vertica, the LIBNAME statement option DEFER=YES is ignored when the LIBNAME statement also contains the CONNECTION=UNIQUE option.

In this situation, connections are opened immediately after you assign the libref and are not deferred to a later time. As a result, the maximum number of connections to Vertica is reached and no further connections can be opened.

An error message similar to the following is then written to the log:

ERROR: CLI error trying to establish connection: [Vertica][VerticaDSII] (160) Connection attempt failed: FATAL 4060:  New session rejected due to limit

ERROR: Error in the LIBNAME statement.

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

Operating System and Release Information

Product Family	Product	System	SAS Release
			Reported	Fixed*
SAS System	SAS/ACCESS Interface to Vertica	Microsoft® Windows® for x64	9.4 TS1M5	9.4 TS1M5
		64-bit Enabled AIX	9.4 TS1M5	9.4 TS1M5
		64-bit Enabled Solaris	9.4 TS1M5	9.4 TS1M5
		HP-UX IPF	9.4 TS1M5	9.4 TS1M5
		Linux for x64	9.4 TS1M5	9.4 TS1M5
		Solaris for x64	9.4 TS1M5	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.

---

A fix for this issue for SAS/ACCESS Interface to Vertica 9.4_M5 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/D6G.html#63178

---

Deferred connections, indicated by the DEFER=YES option, do not work as expected in SAS/ACCESS® Interface to Vertica when the specified connection type is unique.

Type:	Problem Note
Priority:	high

Date Modified:	2019-01-02 13:55:16
Date Created:	2018-11-06 08:28:22