Dynatrace 5.5 PW database migration
Is there any process or Query available to confirm that the PW database has been successfully migrated to 5.5 upon connection from the 5.5 server? Also in a previous question it was asked if a 4.2 agent connecting to a 5.5 collector without a process/iis or jvm restart would be able to collect data. When tested method showed up as <unknown>. Not sure if relatede to DB migration or not.
Thanks Ted
HI John,
There'd be no impact beyond the obvious (no long term measures). The last 1 hour's worth of measures are actually stored in dynaTrace Server memory, so you'd have those measures even without a PW. But, you'd not be able to chart or alert on anything older than one hour.
If you want more than an hour's measures, you have a couple options:
1) Set up a new DB instance for your 5.5 server and leave the 4.2 as is. But, I see that the issue here might be how long it takes to get.
2) You could use PostgreSQL which is a free DB. It's easily downloaded and installed on Windows and you can find it in RPM/Yum, etc. for Linux.
thanks,
ted
On another note...not sure if I should start another thread but what are the implications, if any, to not running a PW at all other than not having the longer term data? Would this affect any applicaiton performance or collections?
Reason I ask is that we have been asked to pilot 5.5 with two of our smaller apps before going live. Looks like embedded really isnt supported with Production any more and I didnt want to take the database from the 4.2 system until we were ready for rest of environments and a new DB takes some time to get.
As far as the PW goes, there is a version table that you could query to see what the version is. There is a Major and Minor column.
As for the 4.2 Agent -> 5.5 Collector, The agent will operate as a 4.2 Agent until it is restarted at which point it will bootstrap to 5.5.
However, if you are seeing <unknown> in the PurePaths then you have a corrupt Collector Cache. This could be do to an incorrect upgrade/migration or to a known issue with a mix of 4.2 and 5.5 agents connected to the same collector. In order to resolve the issue, you'd need to clear the collector cache and restart the agents. You can clear the collector cache in the Settings->dynaTrace Server->Collectors screen.
===ted
