No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Advanced O&M Command Reference

OceanStor 2800 V5 V500R007

This document is applicable to OceanStor 2800 V5. Based on the CLI, this document describes how to use various commands classified by functions and how to set the CLI and manage the storage system through these commands. The document that you browse online matches the latest C version of the product. Click Download to download documents of other C versions.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ccdb.sh

ccdb.sh

Function

The ccdb.sh command is used to query operating information about the CCDB module and rectify faults.

Format

ccdb.sh -c clearccdb [local | peer | all]

ccdb.sh -c cleardbfile [dbName]

ccdb.sh -c cleardblog [dbName]

ccdb.sh -c exportdb

ccdb.sh -c operdb [dbName] [cmdpath]

ccdb.sh -c showstate

ccdb.sh -c showdbinfo

ccdb.sh -c showdb [dbName]

ccdb.sh -c showbackupdb

ccdb.sh -c showmd

ccdb.sh -c startccdb [local | peer | all]

ccdb.sh -c stopccdb [local | peer | all]

ccdb.sh -c recoverymd [cmdpath] [online | offline]

ccdb.sh -c repairdb [db | all] [backupfile | LATEST] [dbName]

ccdb.sh -h

ccdb.sh -a

ccdb.sh -c showccdbdirtyflag [mem | disk | bmc | file]

ccdb.sh -c setccdbdirtyflag [nid] [type] [validFlag]

ccdb.sh -c resetccdbdirtyflag

ccdb.sh -c clearccdbblkraidinfo

ccdb.sh -c showccdbblkraidinfo

ccdb.sh -c closeccdbcrccheck

ccdb.sh -c showccdbcrccheck

ccdb.sh -c showupgradeinfo

ccdb.sh -c setupgradeloginfo [srcVersion] [dstVersion] [status] [raidFlagMap]

ccdb.sh -c clearupgradeloginfo

ccdb.sh -c setsysupgradepath [srcVersion] [dstVersion]

ccdb.sh -c setnodeversion [nid] [version]

ccdb.sh -c setccdbupgradeinfo

ccdb.sh -c addupgradeevent

ccdb.sh -c clearlogservice [logId]

ccdb.sh -c startlogservice [logId]

ccdb.sh -c resetstarttime

ccdb.sh -c checkmd

ccdb.sh -c removemddisk [diskId]

ccdb.sh -c opermd [cmd]

ccdb.sh -c showccdbraiddisk

ccdb.sh -c setfaultdisk [diskId]

ccdb.sh -c handlearbitrateinfo [show | set | clean] [local | all] [nodemap]

ccdb.sh -c handleblkraidxcheckflag [show | set ] [flag]

ccdb.sh -c startnvramadapter [nodemap]

ccdb.sh -c showclusterinfo [startWorkInfo | siteCompatibleVersion] [siteId]

Parameters

Parameter

Description

Value

c clearccdb Cleans up CCDB data from the local engine.

-

c cleardbfile [dbName] Cleans up the database file from the local engine.

"dbName": indicates the name of the service database. To obtain the database name, run the "ccdb.sh -c showdbinfo" command.

Modes

Minisystem mode

Usage Guidelines

This command is used to locate or recover the system cluster configuration database. It can be used only when the cluster configuration database is abnormal. Incorrect use of this command may damage system cluster configurations.

The command functions include:

  • Cleans up CCDB data from the local engine.
  • Cleans up the database file from the local engine.
  • Cleans up the database log file from the local engine.
  • Exports the database file to directory "/home/permitdir/export_import".
  • Operates the database file of the local engine using SQLs.
  • Queries CCDB service status.
  • Queries all database names.
  • Queries database information, including the version and health status.
  • Views the backup log file.
  • Views the block devices used by CCDB.
  • Starts the CCDB service of the local engine.
  • Stops the CCDB service of the local engine.
  • Restores the block devices used by CCDB.
  • Restores the database using the backup file.
  • Displays command help information.
  • Views all commands.
  • Queries dirty data marks.
  • Sets dirty data marks.
  • Resets dirty data marks.
  • Clears CCDB RAID information.
  • Queries CCDB RAID information.
  • Disables CCDB CRC.
  • Queries CCDB CRC.
  • Queries upgrade information.
  • Sets upgrade log information.
  • Clears upgrade log information.
  • Sets system upgrade path information.
  • Sets node version information.
  • Adds CCDB upgrade events.
  • Adds CCDB upgrade information.
  • Clears logservice.
  • Starts logservice.
  • Resets start time.
  • Checks CCDB RAID status.
  • Removes the disk of CCDB RAID.
  • Operates the block devices used by CCDB.
  • Queries disk information in RAID.
  • Sets a fault disk.
  • Operates CCDB arbitration information.
  • Operates CCDB RAID check marks.
  • Starts the CCDB NVRAM service.
  • Queries the cluster information.

Example

  • Clean up CCDB data from the local node.

    Storage: minisystem> ccdb.sh -c clearccdb local
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer server.
    admin:/diagnose>ccdb clearlocal
    clear local CCDB success
    admin:/diagnose>exit
    Storage: minisystem>
  • Clean up CCDB data from the peer node in the local engine.

    Storage: minisystem> ccdb.sh -c clearccdb peer
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    Clear peer CCDB.
    Storage: minisystem>
  • Clean up CCDB data from the local engine.

    Storage: minisystem> ccdb.sh -c clearccdb all
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb clearlocal
    clear local CCDB success
    admin:/diagnose>exit
    Clear peer CCDB.
    Storage: minisystem>
  • Clean up the file of database "DLMDB" from the local engine. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c cleardbfile DLMDB
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb cleardbfile DLMDB
    clear CCDB db file success.
    admin:/diagnose>exit
    Storage: minisystem>
  • Clean up the log file of database "DLMDB" from the local engine. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c cleardblog DLMDB
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb cleardblogfile DLMDB
    clear CCDB db file success.
    admin:/diagnose>exit
    Storage: minisystem>
  • View the command list of "ccdb.sh".

    Storage: minisystem> ccdb.sh -a
    ccdb.sh -c clearccdb [local | peer | all]                                           : clear local-engine ccdb data.
    ccdb.sh -c cleardbfile [dbName]                                                     : clear local-engine db file.
    ccdb.sh -c cleardblog [dbName]                                                      : clear local-engine db log file.
    ccdb.sh -c exportdb                                                                 : force export db file to '/home/permitdir/export_import'.
    ccdb.sh -c operdb [dbName] [cmdpath]                                                : operate local-engine db by SQL.
    ccdb.sh -c showstate                                                                : show ccdb service information.
    ccdb.sh -c showdbinfo                                                               : show all db name.
    ccdb.sh -c showdb [dbName]                                                          : show db information, including version,health degree.
    ccdb.sh -c showbackupdb                                                             : show ccdb backup file.
    ccdb.sh -c showmd                                                                   : show information about block device to be used ccdb.
    ccdb.sh -c startccdb [local | peer | all]                                           : start local-engine ccdb service.
    ccdb.sh -c stopccdb [local | peer | all]                                            : stop local-engine ccdb service.
    ccdb.sh -c recoverymd [cmdpath] [online | offline]                                  : recovery block device to be used ccdb.
    ccdb.sh -c repairdb [db | all] [backupfile] [dbName]                                : auto repair db by the history backup db file.
    ccdb.sh -c showccdbdirtyflag  [mem | disk]                                          : show ccdb dirty flag.
    ccdb.sh -c setccdbdirtyflag [nid] [type] [validFlag]                                : set ccdb dirty flag, [type] is [0|1|2],0:nodeFlag,1:nvram, 2:mem.
    ccdb.sh -c resetccdbdirtyflag                                                       : restore factory settings.
    ccdb.sh -c clearccdbblkraidinfo                                                     : clear ccdb blk raid info.
    ccdb.sh -c showccdbblkraidinfo                                                      : show ccdb blk raid info.
    ccdb.sh -c closeccdbcrccheck                                                        : close ccdb crc check.
    ccdb.sh -c showccdbcrccheck                                                         : show ccdb crc check.
    ccdb.sh -c showupgradeinfo                                                          : show upgrade info.
    ccdb.sh -c setupgradeloginfo [srcVersion] [dstVersion] [status] [raidFlagMap]       : set upgrade log info.
    ccdb.sh -c clearupgradeloginfo                                                      : clear upgrade log info.
    ccdb.sh -c setsysupgradepath [srcVersion] [dstVersion]                              : set sys upgrade path.
    ccdb.sh -c setnodeversion [nid] [version]                                           : set node version info.
    ccdb.sh -c setccdbupgradeinfo                                                       : set ccdb upgrade info.
    ccdb.sh -c addupgradeevent                                                          : add upgrade event.
    ccdb.sh -c clearlogservice [logId]                                                  : clear log service.
    ccdb.sh -c startlogservice [logId]                                                  : start log service.
    ccdb.sh -c resetstarttime                                                           : reset ccdb start work delay time.
    ccdb.sh -c checkmd                                                                  : check ccdb device md200.
    Storage: minisystem> 
  • View the help information about "ccdb.sh".

    Storage: minisystem> ccdb.sh -h
    ccdb.sh [-h] | [-a] | [-c] : It is just a cluster configuration database command. Enter ccdb.sh -a to obtain more information.
    Storage: minisystem>
  • Stop the CCDB service of the local and peer nodes in the local engine.

    Storage: minisystem> ccdb.sh -c stopccdb all
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    Storage: minisystem>
  • Stop the CCDB service of the peer node in the local engine.

    Storage: minisystem> ccdb.sh -c stopccdb peer
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    CCDB stop peer service.
    Storage: minisystem>
  • Query all database backup files.

    Storage: minisystem> ccdb.sh -c showbackupdb 
    backup-2015-09-13-18-00-53.tar backup-2015-09-14-16-58-36.tar backup-2015-09-14-18-51-47.tar
    Storage: minisystem>
  • Export the database file to "/home/permirdir/export_import". This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c exportdb 
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb exportdb /home/permitdir/export_import
    export db success.
    admin:/diagnose>exit
    Storage: minisystem>
  • Query the version and health status of database "DLMDB". This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c showdb DLMDB
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb mountmd
    admin:/diagnose>exit
    DB Name : DLMDB
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/DLMDB_0/DLMDB
    snapshot version
    --------------
    17
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/DLMDB_0/DLMDB
    health
    -----
    ok
    admin:/diagnose>exit
    admin:/diagnose>ccdb unmountmd
    admin:/diagnose>exit
    Storage: minisystem>
  • Query the versions and health status of all service databases. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c showdbinfo 
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb showdbname
    |-- DLMDB_0
    |-- ccdb_metadata.db_0
    | |-- ccdb_metadata.db
    | |-- ccdb_metadata.db-shm
    | |-- ccdb_metadata.db-wal
    | |-- paxos_ccdb_metadata.db-epoch.log
    | `-- paxos_ccdb_metadata.db_1-magic.log
    |-- cmr_db_0_0
    | |-- cmr_db_0
    | |-- cmr_db_0-shm
    | |-- cmr_db_0-wal
    | |-- paxos_cmr_db_0-epoch.log
    | `-- paxos_cmr_db_0_1-magic.log
    |-- dbRepRm.db_0
    | |-- dbRepRm.db
    | |-- dbRepRm.db-shm
    | |-- dbRepRm.db-wal
    | |-- paxos_dbRepRm.db-epoch.log
    | `-- paxos_dbRepRm.db_1-magic.log
    |-- dbRepSdddb_0
    | |-- dbRepSdddb
    | |-- dbRepSdddb-shm
    | |-- dbRepSdddb-wal
    | |-- paxos_dbRepSdddb-epoch.log
    | `-- paxos_dbRepSdddb_1-magic.log
    |-- dbRepSvc.db_0
    | |-- dbRepSvc.db
    | |-- dbRepSvc.db-shm
    | |-- dbRepSvc.db-wal
    | |-- paxos_dbRepSvc.db-epoch.log
    | `-- paxos_dbRepSvc.db_1-magic.log
    |-- dbRepUtil.db_0
    | |-- dbRepUtil.db
    | |-- dbRepUtil.db-shm
    | |-- dbRepUtil.db-wal
    | |-- paxos_dbRepUtil.db-epoch.log
    | `-- paxos_dbRepUtil.db_1-magic.log
    `-- lost+found
     
    8 directories, 30 files
    admin:/diagnose>exit
    Storage: minisystem>
     
    Storage: minisystem> ccdb.sh -c showdb 
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb mountmd
    admin:/diagnose>exit
    DB Name : ccdb_metadata.db
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/ccdb_metadata.db_0/ccdb_metadata.db
    snapshot version
    --------------
    6
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/ccdb_metadata.db_0/ccdb_metadata.db
    health
    -----
    ok
    admin:/diagnose>exit
    DB Name : cmr_db_0
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/cmr_db_0_0/cmr_db_0
    snapshot version
    --------------
    17
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/cmr_db_0_0/cmr_db_0
    health
    -----
    ok
    admin:/diagnose>exit
    DB Name : dbRepRm.db
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/dbRepRm.db_0/dbRepRm.db
    snapshot version
    --------------
    0
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/dbRepRm.db_0/dbRepRm.db
    health
    -----
    ok
    admin:/diagnose>exit
    DB Name : dbRepSdddb
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/dbRepSdddb_0/dbRepSdddb
    snapshot version
    --------------
    0
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/dbRepSdddb_0/dbRepSdddb
    health
    -----
    ok
    admin:/diagnose>exit
    DB Name : dbRepSvc.db
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/dbRepSvc.db_0/dbRepSvc.db
    snapshot version
    --------------
    0
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/dbRepSvc.db_0/dbRepSvc.db
    health
    -----
    ok
    admin:/diagnose>exit
    DB Name : dbRepUtil.db
    ------------------------------------------------------
    admin:/diagnose>ccdb showversion /OSM/ccdb/store/dbRepUtil.db_0/dbRepUtil.db
    snapshot version
    --------------
    128
    admin:/diagnose>exit
    admin:/diagnose>ccdb checkup /OSM/ccdb/store/dbRepUtil.db_0/dbRepUtil.db
    health
    -----
    ok
    admin:/diagnose>exit
    admin:/diagnose>ccdb unmountmd
    admin:/diagnose>exit
    Storage: minisystem>
  • Query CCDB cluster status and heartbeats of nodes in the cluster.

    "Storage: minisystem> ccdb.sh -c showstate
    CCDB cluster heartbeat information:
    --------------------------------------------
    admin:/diagnose>mon showhb
    nid = 0 ,role = 0 (1:M,2:S,3:R),status = 0 (1:R,2:N,3:AbN),is join = 0 ,epoch = 0 ,schema version = 0 ,engineId = 65535 
    nid = 1 ,role = 0 (1:M,2:S,3:R),status = 0 (1:R,2:N,3:AbN),is join = 0 ,epoch = 0 ,schema version = 0 ,engineId = 65535 
    nid = 2 ,role = 0 (1:M,2:S,3:R),status = 0 (1:R,2:N,3:AbN),is join = 0 ,epoch = 0 ,schema version = 0 ,engineId = 65535 
    nid = 3 ,role = 0 (1:M,2:S,3:R),status = 0 (1:R,2:N,3:AbN),is join = 0 ,epoch = 0 ,schema version = 0 ,engineId = 65535 
    admin:/diagnose>exit
    CCDB cluster Finite State Machine information:
    --------------------------------------------
    admin:/diagnose>mon showsm
    [2015-09-14 09:15:58] init(sys set master event)---->recovery
    [2015-09-14 09:18:06] recovery(silent timeout event)---->elect
    [2015-09-14 09:18:06] elect(heartbeat collect event)---->failover_sync
    [2015-09-14 09:18:06] failover_sync(sync master succ event)---->normal
    [2015-09-14 09:18:06] normal(conf event)---->config
    [2015-09-14 09:18:10] config(conf succ event)---->normal
    admin:/diagnose>exit
    Storage: minisystem> 
    "
  • Operate DLMDB and store the operation SQLs in file "/home/permitdir/execsql". This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    "Storage: minisystem> ccdb.sh -c operdb DLMDB /home/permitdir/execsql
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb mountmd
    admin:/diagnose>exit
    admin:/diagnose>ccdb execsql /OSM/ccdb/store/DLMDB_0/DLMDB ""select * from DLM_CCDB_INTERNAL_NODE_EVENT_S;;""
    exec sql statement failed.
    admin:/diagnose>exit
    admin:/diagnose>ccdb unmountmd
    admin:/diagnose>exit
    Storage: minisystem> "
  • Query all service databases. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    "Storage: minisystem> ccdb.sh -c showdbinfo 
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb showdbname
    |-- DLMDB_0
    |-- ccdb_metadata.db_0
    | |-- ccdb_metadata.db
    | |-- ccdb_metadata.db-shm
    | |-- ccdb_metadata.db-wal
    | |-- paxos_ccdb_metadata.db-epoch.log
    | `-- paxos_ccdb_metadata.db_1-magic.log
    |-- cmr_db_0_0
    | |-- cmr_db_0
    | |-- cmr_db_0-shm
    | |-- cmr_db_0-wal
    | |-- paxos_cmr_db_0-epoch.log
    | `-- paxos_cmr_db_0_1-magic.log
    |-- dbRepRm.db_0
    | |-- dbRepRm.db
    | |-- dbRepRm.db-shm
    | |-- dbRepRm.db-wal
    | |-- paxos_dbRepRm.db-epoch.log
    | `-- paxos_dbRepRm.db_1-magic.log
    |-- dbRepSdddb_0
    | |-- dbRepSdddb
    | |-- dbRepSdddb-shm
    | |-- dbRepSdddb-wal
    | |-- paxos_dbRepSdddb-epoch.log
    | `-- paxos_dbRepSdddb_1-magic.log
    |-- dbRepSvc.db_0
    | |-- dbRepSvc.db
    | |-- dbRepSvc.db-shm
    | |-- dbRepSvc.db-wal
    | |-- paxos_dbRepSvc.db-epoch.log
    | `-- paxos_dbRepSvc.db_1-magic.log
    |-- dbRepUtil.db_0
    | |-- dbRepUtil.db
    | |-- dbRepUtil.db-shm
    | |-- dbRepUtil.db-wal
    | |-- paxos_dbRepUtil.db-epoch.log
    | `-- paxos_dbRepUtil.db_1-magic.log
    `-- lost+found
     
    8 directories, 30 files
    admin:/diagnose>exit
    Storage: minisystem> "
  • Query block devices used by CCDB. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c showmd
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb opermd "mdadm --detail /dev/md200"
    /dev/md200:
     Version : 1.2
     Creation Time : Mon Sep 14 17:28:03 2015
     Raid Level : raid1
     Array Size : 2096064 (2047.28 MiB 2146.37 MB)
     Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB)
     Raid Devices : 6
     Total Devices : 6
     Persistence : Superblock is persistent
     
     Update Time : Mon Sep 14 19:01:53 2015
     State : clean 
     Active Devices : 6
     Working Devices : 6
     Failed Devices : 0
     Spare Devices : 0
     
     Name : Storage:CCDB_RAID_DEVICE (local to host Storage)
     UUID : fec7b53d:372104b6:4b575544:a44492cb
     Events : 29
     
     Number Major Minor RaidDevice State
     0 252 48 0 active sync /dev/ld259a
     1 252 304 1 active sync /dev/ld275a
     2 252 4288 2 active sync writemostly /dev/ld12a
     3 252 4304 3 active sync writemostly /dev/ld13a
     4 252 4320 4 active sync writemostly /dev/ld14a
     5 252 4336 5 active sync writemostly /dev/ld15a
     admin:/diagnose>exit
     Storage: minisystem>
  • Start the CCDB service of the local node.

    Storage: minisystem> ccdb.sh -c startccdb local
    admin:/diagnose>ccdb startserver
    start CCDB server success.
    admin:/diagnose>exit
    Storage: minisystem>
  • Start the CCDB service of the peer node in the local engine.

    Storage: minisystem> ccdb.sh -c startccdb peer
    CCDB start peer service.
    Storage: minisystem>
  • Start the CCDB service of the local and peer nodes in the local engine.

    Storage: minisystem> ccdb.sh -c startccdb all
    admin:/diagnose>ccdb startserver
    start CCDB server success.
    admin:/diagnose>exit
    CCDB start peer service.
    Storage: minisystem>
  • Stop the CCDB service of the local node.

    Storage: minisystem> ccdb.sh -c stopccdb local
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    Storage: minisystem>
  • Operate the block devices used by CCDB in offline mode and store operation commands in file "/home/permitdir/execmd". This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c recoverymd /home/permitdir/execmd offline
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb opermd "mdadm --detail /dev/md200" 0
    /dev/md200:
     Version : 1.2
     Creation Time : Mon Sep 14 17:28:03 2015
     Raid Level : raid1
     Array Size : 2096064 (2047.28 MiB 2146.37 MB)
     Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB)
     Raid Devices : 6
     Total Devices : 6
     Persistence : Superblock is persistent
     
     Update Time : Mon Sep 14 19:37:48 2015
     State : clean 
     Active Devices : 6
     Working Devices : 6
     Failed Devices : 0
     Spare Devices : 0
     
     Name : Storage:CCDB_RAID_DEVICE (local to host Storage)
     UUID : fec7b53d:372104b6:4b575544:a44492cb
     Events : 67
     
     Number Major Minor RaidDevice State
     0 252 48 0 active sync /dev/ld259a
     1 252 304 1 active sync /dev/ld275a
     6 252 4288 2 active sync writemostly /dev/ld12a
     3 252 4304 3 active sync writemostly /dev/ld13a
     4 252 4320 4 active sync writemostly /dev/ld14a
     5 252 4336 5 active sync writemostly /dev/ld15a
    admin:/diagnose>exit
    Storage: minisystem>
  • Operate the block devices used by CCDB in online mode and store operation commands in file "/home/permitdir/execmd".

    Storage: minisystem> ccdb.sh -c recoverymd /home/permitdir/execmd online
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    /dev/md200
    admin:/diagnose>ccdb opermd "mdadm --manage /dev/md200 --fail /dev/ld12a" 1
    admin:/diagnose>exit
    Storage: minisystem>
  • Operate the block devices used by CCDB. The operation command is "mdadm -D /dev/md200".

    Storage: minisystem> ccdb.sh -c opermd mdadm -D /dev/md200
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb opermd "mdadm -D /dev/md200" 1 0
    /dev/md200:
            Version : 1.2
      Creation Time : Fri May 18 12:49:38 2018
         Raid Level : raid1
         Array Size : 2096064 (2047.28 MiB 2146.37 MB)
      Used Dev Size : 2096064 (2047.28 MiB 2146.37 MB)
       Raid Devices : 2
      Total Devices : 2
        Persistence : Superblock is persistent
      Intent Bitmap : Internal
        Update Time : Fri May 18 13:04:10 2018
              State : active 
     Active Devices : 2
    Working Devices : 2
     Failed Devices : 0
      Spare Devices : 0
               Name : Storage:CCDB_RAID_DEVICE  (local to host Storage)
               UUID : bca39515:762aa47d:0dea29df:dedc9097
             Events : 16
        Number   Major   Minor   RaidDevice State
           0     252       48        0      active sync   /dev/ld259a
           1     252     4288        1      active sync writemostly   /dev/ld12a
    admin:/diagnose>exit
    Storage: minisystem> 
  • Use file "backup-2015-09-13-18-00-53.tar" to restore the file of DLMDB. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c showbackupdb 
    backup-2015-09-13-18-00-53.tar backup-2015-09-14-16-58-36.tar backup-2015-09-14-18-51-47.tar
    Storage: minisystem> ccdb.sh -c repairdb db backup-2015-09-14-18-51-47.tar DLMDB
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb recoveryccdb 0 backup-2015-09-14-18-51-47.tar DLMDB
    recover CCDB db success.
    admin:/diagnose>exit
  • Use file "backup-2015-09-13-18-00-53.tar" to restore all contents of DLMDB. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c repairdb all backup-2015-09-14-18-51-47.tar DLMDB
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>ccdb recoveryccdb 2 backup-2015-09-14-18-51-47.tar DLMDB
    recover CCDB db success.
    admin:/diagnose>exit
    Storage: minisystem> 
  • Show CCDB dirty flag.

    Storage: minisystem> ccdb.sh -c showccdbdirtyflag mem
    admin:/diagnose>ccdbDirty showmemflag
    nodeid:0, type:0, flag:1 
    nodeid:0, type:1, flag:1 
    nodeid:0, type:2, flag:1 
    nodeid:1, type:0, flag:1 
    nodeid:1, type:1, flag:1 
    nodeid:1, type:2, flag:1 
    nodeid:2, type:0, flag:2 
    nodeid:2, type:1, flag:2 
    nodeid:2, type:2, flag:0 
    nodeid:3, type:0, flag:2 
    nodeid:3, type:1, flag:2 
    nodeid:3, type:2, flag:0 
    nodeid:4, type:0, flag:2 
    nodeid:4, type:1, flag:2 
    nodeid:4, type:2, flag:0 
    nodeid:5, type:0, flag:2 
    nodeid:5, type:1, flag:2 
    nodeid:5, type:2, flag:0 
    nodeid:6, type:0, flag:2 
    nodeid:6, type:1, flag:2 
    nodeid:6, type:2, flag:0 
    nodeid:7, type:0, flag:2 
    nodeid:7, type:1, flag:2 
    nodeid:7, type:2, flag:0 
    admin:/diagnose>exit
    Storage: minisystem> ccdb.sh -c showccdbdirtyflag disk           
    admin:/diagnose>ccdbDirty showdiskflag
     disk dirty flag magic:0xabcd5555. 
     disk dirty flag version:1. 
    nodeid:0, type:0, flag:1 
    nodeid:0, type:1, flag:1 
    nodeid:0, type:2, flag:0 
    nodeid:1, type:0, flag:1 
    nodeid:1, type:1, flag:1 
    nodeid:1, type:2, flag:0 
    nodeid:2, type:0, flag:2 
    nodeid:2, type:1, flag:2 
    nodeid:2, type:2, flag:0 
    nodeid:3, type:0, flag:2 
    nodeid:3, type:1, flag:2 
    nodeid:3, type:2, flag:0 
    nodeid:4, type:0, flag:2 
    nodeid:4, type:1, flag:2 
    nodeid:4, type:2, flag:0 
    nodeid:5, type:0, flag:2 
    nodeid:5, type:1, flag:2 
    nodeid:5, type:2, flag:0 
    nodeid:6, type:0, flag:2 
    nodeid:6, type:1, flag:2 
    nodeid:6, type:2, flag:0 
    nodeid:7, type:0, flag:2 
    nodeid:7, type:1, flag:2 
    nodeid:7, type:2, flag:0 
    admin:/diagnose>exit
  • Set CCDB dirty flag.

    Storage: minisystem> ccdb.sh -c setccdbdirtyflag 0 2 1
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdbDirty setflag 0 2 1
    nodeid:0, type:2, flag:1 successfully. 
    admin:/diagnose>exit
  • Reset CCDB dirty flag.

    Storage: minisystem> ccdb.sh -c resetccdbdirtyflag
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdbDirty setdefaultflag
    set ccdb dirty default flag successfully. 
    admin:/diagnose>exit
  • Clean up CCDB RAID info. This command will stop the CCDB service, and you can perform "ccdb.sh -c startccdb all" to restart the CCDB service.

    Storage: minisystem> ccdb.sh -c clearccdbblkraidinfo
    DANGER: You are going to perform a danger command.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Enter "I have read and understand the consequences associated with performing this operation." to confirm running this command.
    I have read and understand the consequences associated with performing this operation.
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb stopserver
    stop CCDB server success.
    admin:/diagnose>exit
    CCDB stop peer service.
    admin:/diagnose>blkRaid clearBlkRaid 0
    clear module[0] blkRaid ok
    admin:/diagnose>exit
  • Show CCDB RAID info.

     admin:/diagnose>blkRaid showDiskSuper 0
     
    ******************BLK RAID DISK SUPER INFO ***********
    moduleId    = 0x0 
     diskId      = 0x0 
     magic       = 0xabab2015 
     productSn    = 2102350BSJ1055621031 
     serialNum   = 0x6 
     crc         = 0x0 
     Create UTC time   =2017-11-8 : 10 : 51 :40 
     Save UTC time   =2017-11-8 : 10 : 53 :12 
    moduleId    = 0x0 
     diskId      = 0x1 
     magic       = 0xabab2015 
     productSn    = 2102350BSJ1055621031 
     serialNum   = 0x6 
     crc         = 0x0 
     Create UTC time   =2017-11-8 : 10 : 51 :40 
     Save UTC time   =2017-11-8 : 10 : 53 :12 
    moduleId    = 0x0 
     diskId      = 0x2 
     magic       = 0xabab2015 
     productSn    = 2102350BSJ1055621031 
     serialNum   = 0x6 
     crc         = 0x0 
     Create UTC time   =2017-11-8 : 10 : 51 :40 
     Save UTC time   =2017-11-8 : 10 : 53 :12 
    moduleId    = 0x0 
     diskId      = 0x3 
     magic       = 0xabab2015 
     productSn    = 2102350BSJ1055621031 
     serialNum   = 0x6 
     crc         = 0x0 
     Create UTC time   =2017-11-8 : 10 : 51 :40 
     Save UTC time   =2017-11-8 : 10 : 53 :12 
    admin:/diagnose>exit
  • Disable CCDB CRC.

    Storage: minisystem> ccdb.sh -c closeccdbcrccheck
    admin:/diagnose>mon setsqlitecrc 0
    set sqlite crc success.
    admin:/diagnose>exit
  • Query CCDB CRC.

    Storage: minisystem> ccdb.sh -c showccdbcrccheck
    admin:/diagnose>mon showsqlitecrc
    magic:171438283.
    status:1.
    admin:/diagnose>exit
    Storage: minisystem>
  • Query upgrade information.

    Storage: minisystem> ccdb.sh -c showupgradeinfo
    admin:/diagnose>mon showupgradeinfo
    sys upgrade info:
    srcVersion = 0
    dstVersion = 0
    node version info:
    nodeId = 0, version = 0
    nodeId = 1, version = 0
    nodeId = 2, version = 0
    nodeId = 3, version = 0
    nodeId = 4, version = 0
    nodeId = 5, version = 0
    nodeId = 6, version = 0
    nodeId = 7, version = 0
    ccdb upgrade info:
    isValid = 1
    status = 0
    srcFeature = 0
    dstFeature = 0
    curStep = 0
    totalStep = 0
    upgrade log info:
    srcVersion = 0
    dstVersion = 0
    status = 0
    raidFlagMap = 0
    admin:/diagnose>exit
  • Set upgrade log information.

    Storage: minisystem> ccdb.sh -c setupgradeloginfo 6 4 0 0
    admin:/diagnose>mon setupgradelog 6 4 0 0
    set upgrade log success
    src version = 6
    dst version = 4
    upgrade status = 0
    raid valid flag = 0
    admin:/diagnose>exit
  • Clear upgrade log information.

    Storage: minisystem> ccdb.sh -c clearupgradeloginfo
    admin:/diagnose>mon clearupgradelog
    clear ccdb upgrade log success
    admin:/diagnose>exit
  • Set system upgrade path information.

    Storage: minisystem> ccdb.sh -c setsysupgradepath 6 4
    admin:/diagnose>mon setsysupgradepath 6 4
    set sys upgrade path(6 - > 4) success.
    admin:/diagnose>exit
  • Set node version information.

    Storage: minisystem> ccdb.sh -c setnodeversion 0 6
    admin:/diagnose>mon setnodeversion 0 6
    set node = 0 version = 6 success
    admin:/diagnose>exit
  • Add CCDB upgrade events.

    Storage: minisystem> ccdb.sh -c addupgradeevent
    admin:/diagnose>mon startupgrade
    add upgrade event success.
    admin:/diagnose>exit
  • Set CCDB upgrade information.

    Storage: minisystem> ccdb.sh -c setccdbupgradeinfo 
    admin:/diagnose>mon setccdbupgradeinfo
    set ccdb upgrade info success.
    admin:/diagnose>exit
  • Start logservice.

    Storage: minisystem> ccdb.sh -c startlogservice 0
    admin:/diagnose>logService startlogservice 0
    start logservice 0 success.
    admin:/diagnose>exit
  • Clear logservice.

    Storage: minisystem> ccdb.sh -c clearlogservice 0
    admin:/diagnose>logService clearlogservice 0
    clear logservice 0 success.
    admin:/diagnose>exit
  • Reset start time.

    Storage: minisystem> ccdb.sh -c resetstarttime
    admin:/diagnose>mon resetstarttime
    reset start time success.
    admin:/diagnose>exit
  • Check CCDB RAID status.

    Storage: minisystem> ccdb.sh -c checkmd
    admin:/diagnose>ccdb checkmd
    CCDB Raid Status:Normal
    admin:/diagnose>exit
  • Remove disk "ld12a" from CCDB RAID.

    Storage: minisystem> ccdb.sh -c removemddisk ld12a
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    remove md disk /dev/ld12a of md200 success
  • Query disk information in RAID.

    Storage: minisystem> ccdb.sh -c showccdbraiddisk
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    admin:/diagnose>ccdb showraiddisk
    md200 include disks: none.
    md200 available disks:  /dev/ld259 /dev/ld12
    admin:/diagnose>exit 
  • Set a fault disk.

    Storage:~ # ccdb.sh -c setfaultdisk 1090519040
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    ibc_os_hs:/diagnose>ccdb setfaultdisk 1090519040
    set fault disk success.
    ibc_os_hs:/diagnose>exit
  • Operate CCDB arbitration information.

    Storage:~ # ccdb.sh -c handlearbitrateinfo show all
    DANGER: You are going to perform a danger command, this behavior causes database service interruption.
    Suggestion: Before you perform this operation, make sure that the operation will not affect working of system.
    Have you read danger alert message carefully?(y/n)
    y
    Are you sure you really want to perform the operation?(y/n)
    y
    ibc_os_hs:/diagnose>blkRaid showCcdbArb all
    read ccdb node arb view success: 3.
    ibc_os_hs:/diagnose>exit
  • Operate CCDB RAID check marks.

    Storage:~ # ccdb.sh -c handleblkraidxcheckflag show
    ibc_os_hs:/diagnose>blkRaid showCheckFlag
    blk raidx show flag success, flag=0.
    ibc_os_hs:/diagnose>exit
  • Start the CCDB NVRAM service.

    Storage:~ # ccdb.sh -c startnvramadapter 3
    ibc_os_hs:/diagnose>nvramadapter startwork 3
    start nvram adapter success.
    ibc_os_hs:/diagnose>exit
  • Query the cluster information.

    Storage: minisystem> ccdb.sh -c showclusterinfo startWorkInfo
    ibc_os_hs:/diagnose>mon showsw
    [2019-12-23 10:07:30]          CCDB Nvram          SUCCESS   
    [2019-12-23 10:07:30]          CCDB Mon            SUCCESS   
    [2019-12-23 10:07:42]          DLM                 SUCCESS   
    [2019-12-23 10:07:56]          CROS_CLS            SUCCESS   
    ibc_os_hs:/diagnose>exit

System Response

None

Translation
Download
Updated: 2020-01-17

Document ID: EDOC1000181575

Views: 731077

Downloads: 32

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next