Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Cachestore flush


Cachestore flush

Author
Message
jitendra.padhiyar
jitendra.padhiyar
SSC Veteran
SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)

Group: General Forum Members
Points: 248 Visits: 669
Hello Masters,

Again need your help .. :-)

During monitoring I found one of my database in restoring mode from last two days..!!upone checking event logs I found some cachestrore flush error..its new to me but looking like some memory error. The event log error is like below:

"SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations."

"SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations."

"SQL Server has encountered 2 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations."

"The database 'Imagine2013' is marked RESTORING and is in a state that does not allow recovery to be run. "


There is enough disk space available (about 800GB free space) and size of database is just 12GB. I dont think restoration of 12GB db take two days !!!

Any suggestion welcome...!!
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47261 Visits: 44392
Cache store flush is not going to cause any problems with a restore. Other way around, restoring a database will flush the caches. It's not an error, just SQL notifying you that some operation (like a restore) required the caches to be cleared.

If the database is still in the restoring state, good chance that whoever restored it restored WITH NORECOVERY. That means restore the DB and leave it in the restoring state.

Maybe ask whoever restored the DB what command they ran.


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


jitendra.padhiyar
jitendra.padhiyar
SSC Veteran
SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)SSC Veteran (248 reputation)

Group: General Forum Members
Points: 248 Visits: 669
Thanks Gail for the explanation!

I went to properties and set the Max memory to 14GB(Total RAM 16GB) which was before by default. And
now its in normal online mode, and can access it now. Still do not know why it took too much time(2 days) to restore database of just 12GB ??!
GilaMonster
GilaMonster
SSC-Forever
SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)SSC-Forever (47K reputation)

Group: General Forum Members
Points: 47261 Visits: 44392
jitendra.padhiyar (1/24/2013)
I went to properties and set the Max memory to 14GB(Total RAM 16GB) which was before by default. And
now its in normal online mode, and can access it now.


That's not going to be the cause of the problem or the resolution. Good thing to do nonetheless.

Still do not know why it took too much time(2 days) to restore database of just 12GB ??!


Someone went back in and ran RESTORE DATABASE <database name> WITH RECOVERY most likely.


Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search