Technical troubleshooting and more

In case you are doing a full restore and you verify the completeness of your backups  by listbackup and quick check tasks  simply go to your catalog folder   cd /catalog/VERTICADB/  and move the underlying catalog folder (rename it) [VERTICADB:/catalog/VERTICADB] mv v_verticadb_node0001_catalog/ move_v_verticadb_node0001_catalog/ run restore command again, good luck

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)

when trying to create a resource pool using some % of the total CPUs you may encounter this error: Vertica Request for 10% percent of 4 CPUs rounds to zero CPUs \n (6006) (SQLExecDirectW) why? since 10% of 4, rounded by vertica to 0. and you can allocate 0 CPUs to a resource pool how to fix: fix % to be at least 25% or use static allocation of CPU set to a resource pool