To provide redundancy and failover, the PI Data Archive Server can be configured as a collective, which consists of a primary collective member and one or more secondary members. In this scenario, there are two requirements:

• You need to be able to see the collective member information.
• You need to be able to specify which collective member to connect to.

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

This hot fix supplies the following options to address these requirements.

• The virtual table PICONNECTION option mirrors the table by the same name that is used in the PI OLEDB provider. This option lists various collective-related information, including the name of the currently connected member and its primary versus secondary designation.
   
• The LIBNAME option COLLECTIVE_MEMBER forces the connection to use a desired member. Typically, you should not use this option since it defeats the redundancy principle of the collective. However, if you need a connection to a specific member (for example, when investigating a problem), you can use this option to either specify a desired member by name or to specify primary or secondary. If there are multiple secondary members, it is recommended that you specify the member name explicitly.

Note: Due to the architectural limitations of the WebAPI at the time, this feature is NOT supported when you use the PI Web API on UNIX systems.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS/ACCESS Interface to the PI System	Microsoft® Windows® for x64	9.43	9.43	9.4 TS1M5	9.4 TS1M5
		64-bit Enabled AIX	9.43	9.43	9.4 TS1M5	9.4 TS1M5
		64-bit Enabled Solaris	9.43	9.43	9.4 TS1M5	9.4 TS1M5
		HP-UX IPF	9.43	9.43	9.4 TS1M5	9.4 TS1M5
		Linux for x64	9.43	9.43	9.4 TS1M5	9.4 TS1M5
		Solaris for x64	9.43	9.43	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 the PI System 9.44 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/F8X.html#65462

---

A fix for this issue for SAS/ACCESS Interface to the PI System 9.43 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/D3W.html#65462

---

The PI Data Archive Server might be configured as a collective, which consists of a primary collective member and one or more secondary members. This hot fix adds options (virtual table PICONNECTION and LIBNAME option COLLECTIVE_MEMBER) to help control the behavior of the collective.

Type:	Usage Note
Priority:

Date Modified:	2020-02-10 14:01:33
Date Created:	2020-01-28 14:44:20