I just deleted the _SearchDB_ file in my project for the third time since July.
Is deleting _SearchDB_ just a regular part of maintenance for projects? As in "Oh, search don't work. Time to delete the _SearchDB_ file...."
Hi are you using Phrase find? What issue did you have why you needed to delete the search db? When you tried to do searches nothing showed for your search results?
I've used Media Composer for a very long time and haven't needed to ever delete that. Dud you update Media Composer mid project then this issue started? If do could be your user settings.
Look forward to hearing from you.
Kind regards,
Leo
Not using PhraseFind. Using Script Sync. Issues with searching in the Find Clips and Sequences tab. Type a search term. Click Find. Big red error came up and would not search. Deleting the _SearchDB_ file fixed it. Until it happens again.
Although last season I wasn't using Script Sync either on Mac Pro 2010 tower and the same error happened. Was using ISIS storage in both cases for projects and media. Don't recall this happening on local storage.
I haven't used Script sync in a long time, maybe you can report this to Avid incase they know chime in why this needs manually deleting?
It's random and I don't know how to re-create the issue so it would be difficult to get support on this unless support had a way to recreate it on their end. Last season's Mac Pro was a Pivotal Post rental and when I contacted Pivotal about the issue I was told to delete the folder containing _SearchDB_ file in order to fix it. After doing this so many time I realized that deleting just _SearchDB_ was enough to fix the issue without resetting all other non-Find related settings. This season's iMac is mine but the project and media are still saved to Pivotal Post's ISIS. And it's a new project this season, saved to the same location. Script Sync wouldn't be a factor since I didn't use it last season and encountered the error then -- I just brought it up because you mentioned Phrase Find, which I don't have.
Here's one of those random occurances -- #4 since July.
"Search Error: SQL could not be executed"
Where is your SearchDB? On the shared storage, or on your local drives?
I find many SearchDB errors are fixed by moving the database to local. In the find window click the gear-icon next to "Bin Index" in the lower left. There's a pull down menu that says "Default", switch it to "Local Default".
If the project is on shared ISIS storage, do I have such a choice as you illustrate?
Yes. I believe it has little meaning except when working on shared storage (if you don't have shared storage the default and local are the same thing).
The last three places I worked at on shared-storage all had me do this.
© Copyright 2011 Avid Technology, Inc. Terms of Use | Privacy Policy | Site Map | Find a Reseller