There is currently update running on database. Please wait for it to finish to data become accurate

Question

on Friday 9/5 we upgraded to NTA 4.0.3 from NTA 4.0.2, ever since the main NTA summary page is showing a message:

"There is currently update running on database. Please wait for it to finish to data become accurate"

It is now Thursday 9/11 - seems like almost a week to run a database update is excessive.

alankar.srivastava · Answer

I am also getting the same error and unable to see the historical data.

cobrien1 · Answer

Sounds like a different issue.  Support ticket is probably the best route.  Could you provide your ticket number for tracking?

stacy.wood · Answer

This message - There is currently update running on database. Please wait for it to finish to data become accurate.

Is still displaying on our NTA summary page one month later.

We upgraded from NTA 4.0.2 to 4.0.3 prior to the message. And ever since (at least 1 month at this point) it has said there is an update running.

I asked support in regard to another ticket we had open as a result of this upgrade and was told –

It can take several days for that banner to disappear. I have seen it take a week or so.
  It is not something to be worried about.

Ok… but it has been running a month now…

The reply above on this thread that says:

This is the data conversion from the NTA v3 SQL storage to the NTA v4 FlowStorage, and depending on

* how much Netflow data you have
* how much Netflow data you're currently capturing (which is being written direct to the FlowStorage database)
*  whether you installed the FlowStorage datastore on a dedicated server (recommended)
*  whether the FlowStorage server meets or exceeds the recommended system requirements
*  and how busy your Orion server is servicing other applications

will determine how long the data conversion takes.

Really? Does upgrading from NTA 4.0.2 – 4.0.3 result in a conversion of the NTA v3 storage? Didn’t this already occur when we went to 3.x to 4.0?  that finished and the message went away.  Regardless of how much Netflow data we have and are capturing, it shouldn’t take this long. And yes, we have a separate datastore server.  And yes the storage server exceeds requirements.

I've opened another ticket.