Impact does not reconnect back to Primary Object Server

Technote (troubleshooting)


Problem(Abstract)

Impact Server is connected to the Backup Object Server at some stage but unable to connect back to the Primary Object Server.

Symptom

Creating another Event Reader to connect to the Primary Object Server is also failing with the following error:

Error Initializing the Service. Please look at netcool.log for more details. Reason:

com.micromuse.response.event.EventFeedDriverException: java.util.concurrent.TimeoutException


Diagnosing the problem

Check whether or not client is running "Standard failover".


Resolving the problem

As per Impact product documentation,

Standard failover is a configuration in which an SQL database DS switches to a secondary database server when the primary server becomes unavailable and then continues using the secondary until Netcool/Impact is restarted. If the secondary server becomes unavailable, the SQL database DSA will attempt to resume connections using the original primary.

Restart the Impact Server for it to reconnect back to the Primary Object Server.

Product Alias/Synonym

Impact

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Netcool/Impact

Software version:

5.1.1

Operating system(s):

AIX, Linux, Solaris, Windows

Reference #:

1516633

Modified date:

2013-04-04

Translate my page

Machine Translation

Content navigation