Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

Buffering and High Availability

Configure the PICOLLECTIVE and PISERVER tables on the primary server

Configure the PICOLLECTIVE and PISERVER tables on the primary server

  • Last UpdatedOct 22, 2025
  • 2 minute read

Use piconfig to create one record in the PICOLLECTIVE table for the collective and to create a record for each server in the collective in the PISERVER table. You only need to specify identifying fields.

Field

Description

Example

PICOLLECTIVE Identifying Fields

Name

Name of PI collective. Use the host name of an PI Server selected to become the primary member.

uc-sl

Description

Text describing collective.

UC 2006 Demo Collective

CollectiveID

UID of collective. Use the SID of the existing PI Server selected to become the primary member.

08675309-0007-0007-0007- 000000001001

PISERVER Identifying Fields

Name

Host name of machine running PI Server.

uc-sl

Description

Text describing PI Server

UC 2006 Demo Server 1

Collective

Name of the PI Collective containing server. Must match Name in PICOLLECTIVE table.

uc-s1

FQDN

Fully-qualified domain name for host machine.

uc-s1.osisoft.int

Role

Role of server in collective:

  • 0 – Not replicated

  • 1 – Primary server

  • 2 – Secondary server

1

ServerID

PI ServerID. Unique identifier typically generated by the machine hosting PI Server.

Note: Do not modify this value; it is system-generated and required for collective integrity.

08675309-0007-0007-0007-000000010001

We recommend creating a command file and using piconfig to run the commands in that file.

  1. Create a text file, such as collective_create_uc.txt, in the ..\PI\adm directory.

  2. Copy the following template into your new file, then edit it to specify the information for your collective and servers. Replace all {PLACEHOLDER} values with your actual information, and add additional lines for more servers if needed.

    * ============================

    * PICOLLECTIVE + PISERVERS (piconfig command file)

    * Fill the {PLACEHOLDER}s with your real values

    * ============================

    * --- Collective (must exist once) ---

    @tabl picollective

    @mode create,t

    @istr name,Description,CollectiveID

    uc-s1,UC 2006 Demo Collective,{COLLECTIVE_GUID} ; e.g., 08675309-0007-0007-0007-000000001001

    * --- Server members (one row per server) ---

    @tabl piservers

    @mode create,t

    @istr name,Description,Collective,FQDN,Role,ServerID

    uc-s1,UC 2006 Demo Server 1,uc-s1,uc-s1.osisoft.int,1,{SERVER1_ID} ; Role 1 = Primary

    uc-s2,UC 2006 Demo Server 2,uc-s1,uc-s2.osisoft.int,2,{SERVER2_ID} ; Role 2 = Secondary

  3. Open a command window.

  4. Navigate to the ..\PI\adm directory.

  5. Enter: piconfig < collective_create_uc.txt

TitleResults for “How to create a CRG?”Also Available in