SQLite FTS5 index rebuild and search repair
Oyma utilizes an embedded SQLite database with the FTS5 (Full-Text Search 5) extension to deliver sub-30ms search queries across tens of thousands of notes. If external file edits or third-party file modifications cause search discrepancies, you can force a complete index rebuild.
When to rebuild the search index
Consider rebuilding your index if:
- Newly created notes do not appear in Command Palette search (⌘O).
- Search results return deleted notes that no longer exist on disk.
- Keyword queries return inaccurate line number highlights.
Rebuilding the index from application settings
- Open Settings › Vault › Search Index.
- View your current index stats (Total indexed notes, index size on disk, last indexed timestamp).
- Click Rebuild Search Index.
- A progress bar will scan your vault directory, parse CommonMark syntax, and rebuild the FTS5 token table.
Manual index wipe via Terminal
If the application cannot open due to a corrupted SQLite cache file:
- Quit Oyma completely (⌘Q).
- Open Terminal and remove the cached search database:
rm -f ~/Library/Caches/Oyma/search-index.sqlite* - Relaunch Oyma. The application will detect the missing database and regenerate the index automatically in the background.
Related guides
- Search navigation in Search and command palette.
- Vault linking in Linking and backlinks.
- Obsidian compatibility in Obsidian vault setup.
Questions
Where is the SQLite search index located?
The SQLite index file is stored in your local application cache at `~/Library/Caches/Oyma/search-index.sqlite`.
Does rebuilding the search index risk my Markdown files?
No. The search index is purely a derived cache. Your Markdown notes in your vault remain completely untouched.
How long does full re-indexing take?
On Apple silicon, SQLite FTS5 indexes approximately 10,000 notes in under 15 seconds.