Hi All, Sometimes, especially working on virtual environments, file system can become "read only" to protect from corruptions and other failures if Vertica nodes data/catalog file systems become read only, you probably face this error after trying to restart the cluster and even the spread The solution for was to fix "read only" issues (even with just restarting the VM for most of the cases) then start Vertica with the latest good epoch this error: vertica 4803 error: no such file or directory will appear in the spread log (dbLog)
this site will guide you how to overcome some problems you may face during your work and guide you how to perform simple technical operations to achieve your goals.