HDR Secondary Operations

Introduction

HDR cluster consists of Primary and Secondaries. InformixHQ treats every server added as individual server. Depending upon server type in cluster, Informix Server allows or restricts certain acions on specific server types.

From 14.10.XC7 (InformixHQ v.1.6.0) onwards, InformixHQ has handled all such operations on secondary servers in the cluster.

User needs to add primary as well as secondaries in InformixHQ as different servers.

HDR Secondary in Informix HQ

Server type is available on server card with different colour for each type. Servers apart from Primary & Standard types have “Updatable" or “Read-Only" access mode.
1-Root_Page
N/A will be shown for the server that is offline since InformixHQ can not determine the type of the Informix server if unable to connect with it in the first place. It will be updated in scenarios mentioned in Server types and access mode update scenarios.
2-Root_Page
HDR banner on each page is shown for servers apart from Primary & Standard types. HDR banner contains server type and server access mode.
hdr_banner2
Operations that are not allowed on HDR Secondary are disabled in UI with a pop-up message that shows server type and access mode. For more details, refer HDR Secondary operations allowed/disallowed.
hdr_sec_btn_disable

HDR Secondary operations allowed/disallowed

Following table lists the HDR operations allowed/disallowed based on different types of the Informix servers and its access modes in InformixHQ.
HDR Seconday operations allowed/not allowed
Operation Primary Secondary RSS SDS
Updatable Read-only Updatable Read-only Updatable Read-only
Run Checkpoints, Automatic checkpoints ON/OFF Yes No No No No No No
Privileges: SQL Admin API -> Grant, Edit and Revoke Privileges Yes Yes No Yes No Yes No
Privileges: Databases -> Grant, Edit and Revoke Yes Yes No Yes No Yes No
Privileges: Tables -> Grant, Edit and Revoke Yes Yes No Yes No Yes No
SQL Tracing: Enable, Suspend, Resume and Disable Yes Yes Yes Yes Yes Yes Yes
Memory-> Low Memory Manager Edit Yes Yes No Yes No Yes No
Schema Manager-> Create, Drop Database Yes Yes No Yes No Yes No
Virtual Processor-> Add and Drop VPs Yes Yes Yes Yes Yes Yes Yes
Spaces-> Create, Edit, Delete, Add Chunk and Extend Space Yes No No No No No No
Chunks->Add, Edit, Delete, and Extend Chunk Yes No No No No No No
Pools->Add, Edit, and Delete Entry Yes Yes No Yes No Yes No
Backup: Configuration-> Edit and Delete Yes No No Yes Yes No No
Backup: Status-> Run Level 0,1,2 backup Yes No No Yes Yes No No
Recovery Logs-> Move, Add, Delete and Switch Log Yes No No No No No No
Session-> Kill Session Yes Yes Yes Yes Yes Yes Yes
Note: Above table is based on InformixHQ v1.6.0. Some permissions may vary depending on specific Informix server version.

Server types and access mode update scenarios

Following are the cases when Informix server type and access mode are updated in UI on root page in InformixHQ:
  • On running InformixHQ server post v1.5.0 --> When InformixHQ server is started (run HQ Jar) post version 1.5.0, it connects and fetches Informix server types and access mode of all the Informix servers which are added in InformixHQ and are online.
  • InformixHQ Agent is connected --> If Informix server is online and InformixHQ Agent is connected to it. Agent fetches Informix server type and access mode and following are the cases for it:
    1. Case 1 - Via JDBC connection: If InformixHQ agent is running on a remote host other than Informix server.
    2. Case 2 - Via onstat - command : If InformixHQ agent is running on the same host where Informix server is running.
  • Open server card:-> When user opens server information page and Informix server is online.

Failover scenarios in InformixHQ

User needs to add both primary and secondary servers in InformixHQ to monitor them separately. In case of failover InformixHQ Agent will not be able to connect to failed server and there will be no monitoring data collection. User needs to take corrective action as explained below to continue with HQ Agent data collection.
  1. Case 1 - Primary & Secondary servers have same repository database on primary server:
    In this case if primary server fails/is offline, user has to manually change the repository database server configuration in secondary server which is added in InformixHQ. For example:
    case-1-1
    case-1-2
    As primary server is offline, changed repository server to secondary.
    case-1-3
  2. Case 2 - Primary & Secondary servers have same repository database on secondary(updatable) server:

    In this case if secondary server fails/is offline, user manually has to change the repository database server configuration in the primary server which is added in InformixHQ. This case is just vice versa of case 1 which is described above.

  3. Case 3 - Primary & Secondary servers have their respective repository database on their server itself:

    In this case each server has its own repository database, so user does not need to do any configuration changes in HQ agent setup page in case of failover.