After a failover, when the secondary DA came online, things appeared to be working at first but on further investigation, the following was noticed:
a. Sync failed
b. DCs could not connect
c. ../rest/devices showed ONLY the Data Aggregator
d. DA karaf.log showed messages regarding issues reading iRep
WARN | esponseHandler-| - - : : , | AbstractPollResponse | re.common.AbstractPollResponse$ | m.ca.im.data-mgmt.common | | Attribute id does not exist in poll group ; DC out of sync?
ERROR | plyEnvSensorInfo |- - : : , | ExceptionLog | .ca.im.core.util.ExceptionLogger | m.ca.im.common.core.util | | = : Look up requested DCM ID hostname:dbd24d69-ea0f- -bede- ff82c3e7b82 but iRep did not any items. : For input :
The Data Aggregator user was set differently for the Secondary Data Aggregator
Release : 20.2
Component : CA Performance Center
The /opt/IMDataAggregator/apache-karaf-2.4.3/etc/dbconnection.cfg file should be the same between both Data Aggregators. When the Secondary Data Aggregator is not running, copying the primary (working) dbconnection.cfg over the top of the secondary (not working) dbconnection.cfg should allow the Secondary Data Aggregator to start properly.