Pervasive.SQL Control Center Needs to be Restarted in a WAN After a Switch or Failover

Follow

Summary

This Knowledgebase article describes a workaround for a known issue when Pervasive SQL is used in a Neverfail Heartbeat environment.


More Information

Symptoms

When Pervasive PSQL is deployed with Neverfail Heartbeat in a WAN where different IP addresses are used for the Primary and Secondary servers, clients will not experience a seamless switchover.

Cause

Although Neverfail Heartbeat updates the DNS entry for the server name, the Pervasive PSQL Control Centre cannot update its connection information.

Resolution

To overcome this, the Pervasive.PSQL Control Centre must be restarted after a switchover or a failover in a WAN implementation. To improve the reconnection behavior, the Auto Reconnect property should be enabled for all the clients – even so, the clients will still need to reconnect. To enable this option select Local Client->MicroKernel Router->Client Communication Protocol > Enable Auto Reconnect .


Applies To

All Versions


Related Information

None

KBID-940

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.