Performance Warehouse connect using script
Is it possible to (re)connect the Performance Warehouse using some kind of scripting instead of using the GUI? From time to time the Performance Warehouse does not connect when the dT server (5.5) is restarted. Reconnecting the PWH through a script will prevent dataloss; the script can execute when the alert is triggered.
Wim.
OK, thx.
Hi,
I am currently not aware of a possible rest call to trigger a connect to the pwh. However I'll try to summarize what the PWH component is able to do:
- connection loss during normal operation -> constantly trying to reconnect especially we will never give up !
- not being able to during initial connect (first connect, server start, server restart) -> there no reconnect will be done as we do require at least one successful connect to the pwh backend to start up the reconnect mechanism (e.g. prevent reconnect loop in case of bad credentials etc...)
So I assume during restart of dtServer it is possible that a connection attempt is failing and therefore nor automatic reconnect is done. It would be interesting to have server log during such a situation if possible. Additionally I'll forward this question about rest interfaces to a colleague of mine (getting state of PWH, trigger a connect of PWH).
-stefan
In this case the reason for failure is:
2014-02-11 04:28:48 SEVERE [DefaultRepositoryExceptionHandler] Could not handle exception. See attached exception: Cannot open database "dynatrace_prod" requested by the login. The login failed.: com.dynatrace.diagnostics.repository.exceptiontranslators.DefaultRepositoryExceptionHandler handleException:71
Which is strange as it was a "standard" server restart.
Wim.
Is the dynatrace server on the same machine as the database server?
If yes, the startup of the dynatrace server is before the sql server there so the sql server is not ready at this moment. The first connection attempt is failing so we do not perform any reconnect.
quick fixes:
- although we do not recommend it running the dynatrace server on the same machine as the database server try to change the startup procedure that the sql server is started before the dynatrace server
-stefan
