Skip to main content

@v_vdb_node0005: VX001/2973: Data consistency problems found; startup aborted

While trying to start one of Vertica nodes you may face a data consistency problem.

from vertica.log

<PANIC> @v_vdb_node0005: VX001/2973: Data consistency problems found; startup aborted
        HINT:  Check that all file systems are properly mounted.  Also, the --force option can be used to delete corrupted data and recover from the cluster
        LOCATION:  mainEntryPoint, /scratch_a/release/svrtar5575/vbuild/vertica/Basics/vertica.cpp:1613


so.. don't PANIC :-)

solution:

restart the problematic node with force flag which will repair the corruptions from buddy nodes.

 [dbadmin ]$ /opt/vertica/bin/admintools -t restart_node -d $db_name -s $host --force

and the result:

*** Restarting nodes for database vdb ***
        restart host node0005 with catalog v_vdb_node0005_catalog
        issuing multi-node restart
        Starting nodes:
                v_vdb_node0005 (node0005)
        Starting Vertica on all nodes. Please wait, databases with large catalog may take a while to initialize.
        Node Status: v_vdb_node0001: (UP) v_vdb_node0005: (DOWN)
        Node Status: v_vdb_node0001: (UP) v_vdb_node0005: (DOWN)
        Node Status: v_vdb_node0001: (UP) v_vdb_node0005: (DOWN)
        Node Status: v_vdb_node0001: (UP) v_vdb_node0005: (DOWN)
        Node Status: v_vdb_node0001: (UP) v_vdb_node0005: (RECOVERING)
        Node Status: v_vdb_node0001: (UP) v_vdb_node0005: (UP)


Comments

  1. ClaudiaJanuary 22, 2019 at 5:53 AM



    Hello,

    What if I encounter this situation on a single node?
    I tried to use this command :
    /opt/vertica/bin/admintools -t restart_node -d $db_name -s $host --force
    but since there is only a single node, restart doesn't work.

    Can you help me with that?

    Thanks a lot!

    ReplyDelete
  2. AceFebruary 21, 2019 at 12:18 AM

    try to restore using "rollback database to last good Epoch" - in the advanced menu

    ReplyDelete

Post a Comment

Popular posts from this blog

Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed

When trying to apply patch you may face this error the solution is described below. ERROR: bash-4.2$ ../opatch apply Oracle Interim Patch Installer version 12.2.0.1.5 Copyright (c) 2016, Oracle Corporation.  All rights reserved. Oracle Home       : /oracle/app/oracle/product/12.1.0 Central Inventory : /oracle/app/oracle/oraInventory    from           : /oracle/app/oracle/product/12.1.0/oraInst.loc OPatch version    : 12.2.0.1.5 OUI version       : 12.1.0.2.0 Log file location : /oracle/app/oracle/product/12.1.0/cfgtoollogs/opatch/opatch2016-07-27_16-27-44PM_1.log Verifying environment and performing prerequisite checks... Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite check "CheckSystemCommandAvailable" failed. The details are: Missing command :fuser Prerequisite ...
1 comment
Read more

ORA-27104: system-defined limits for shared memory was misconfigured

I faced this error while trying to restore & recover of a PDB (pluggable database) part of the log file and the solution is described here below: log: initialization parameters used for automatic instance: db_name=CDB db_unique_name=gbux_pitr_PDB1_CDB compatible=12.1.0.2.0 db_block_size=8192 db_files=200 diagnostic_dest=/oracle/app/oracle _system_trig_enabled=FALSE sga_target=1888M processes=200 db_create_file_dest=/oracle/auxilary log_archive_dest_1='location=/oracle/auxilary' enable_pluggable_database=true _clone_one_pdb_recovery=true #No auxiliary parameter file used starting up automatic instance CDB RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of recover command at 07/31/2016 16:22:20 RMAN-04014: startup failed: ORA-27104: system-defined limits for shared...
6 comments
Read more

ora-65035 while create pluggable database from another one

or : ORA-21000: error number argument to raise_application_error of -65035 is out of range Cause: this error caused because of an unrecoverable transaction in the source DB. Solution: 1. either stop and start your pluggable source DB 2. identify the open transaction and kill it if you can. use this query to do so: select * from v$transaction t,v$session  s where t.ses_addr = s.saddr;
Post a Comment
Read more