2.100 pdrisechk (Check the configuration of Real Time SAN Replication)

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Rules
(6) Notes

(1) Function

The pdrisechk command checks data integrity of the system definitions required to apply Real Time SAN Replication, and of the pair attributes, pair status, and fence levels of the pair logical volume groups that are provided for HiRDB files.

Before executing this command, make sure that RAID Manager is running.

(2) Executor

HiRDB administrator

(3) Format

 pdrisechk [-d {all|db|sys}] [{-u unit-identifier|-s server-name}] [-l[-n]] [-r]

(4) Options

(a) -d {all|db|sys}

Specifies the types of files to be checked:

all: RDAREAs and system files

db: RDAREAs

sys: System files

(b) -u unit-identifier ~<identifier> ((4 characters))

Specifies the identifier of a unit that is to be checked. If the -u and -s options are both omitted, the command checks the entire HiRDB.

(c) -s server-name ~<identifier> ((1-8))

Specifies the name of a server that is to be checked.

(d) -l

Specifies that when the log-only synchronous method is used, the command is to check whether or not the system configuration is correct at the log application site.

(e) -n

Specifies that the status of a status file for log application processing is not to be checked. The -n option can be specified only when the -l option is specified.

(f) -r

Specifies that when the log-only synchronous method is used, the command is to check whether or not the system configuration allows preparation for log application for pair logical volume groups.

(5) Rules

  1. You can execute the pdrisechk command whether or not HiRDB is active.
  2. The pdrisechk command can be executed when all instances of RAID Manager that were specified in the HORCMINST operand of $PDCONFPATH/pdsys are active at the site where the pdrisechk command was executed.
  3. Execute the pdrisechk command at the server machine that contains the single server or where the system manager is located.
  4. The pdrisechk command checks the contents of the system definition file under $PDCONFPATH.
    Note that $PDCONFPATH is the value specified in the PDCONFPATH operand in the unit control information definition file (if the operand is omitted, $PDDIR/conf is assumed).
  5. The pdrisechk command queries an instance of RAID Manager that was specified in HORCMINST in the system common definition. If the HORCMINST operand is omitted from the system common definition but the pdrisechk command is executed, the value of the HORCMINST environment variable is used as the instance number of RAID Manager.
  6. The table below shows the relationship between the file type to be checked and the -d option for the all-synchronous, hybrid, and log-only synchronous methods. For the synchronous method, the command checks the configuration for all file types regardless of the -d option value.

    Table 2-26 Relationship between the file type to be checked and the -d option

    File typeTarget pair logical volume group name-d option value
    all or omittedsysdb
    DBaaaa_bb....bb_DBYNY
    LOGaaaa_bb....bb_LOGYYN
    SPDaaaa_bb....bb_SPDYYN
    USTSaaaa_cccc_USTSYYN
    SSTSaaaa_bb....bb_SSTSYYN
    Legend:
    aaaa: HiRDB identifier
    bb....bb: Server name
    cccc: Unit identifier
    Y: Checked
    N: Not checked
  7. The table below shows the relationship between the check items for the pdrisechk command and the processing method for Real Time SAN Replication.

    Table 2-27 Relationship between check items for the pdrisechk command and the processing method for Real Time SAN Replication

    No.Check itemProcessing method for Real Time SAN Replication
    All synchronous methodAll asynchronous methodHybrid methodLog-only synchronous method
    1Whether or not the operands required to use Real Time SAN Replication have been specifiedYY
    2Whether or not the optional program products have been set up as required in order to use Real Time SAN ReplicationNY
    3Whether or not the site is in the following status:
    When -l option is specified:
    Log application or Preparation
    When -l option is omitted:
    Transaction execution or Preparation
    NY#1
    4Whether or not all pair logical volume groups requiring an update copy are availableYY
    5Whether or not the pair logical volume group in 4 above has the volume attribute shown in Table 2-28 List of volume attributes checked by the pdrisechk command (when the -l option is specified and in Table 2-29 List of volume attributes checked by the pdrisechk command (when the -l option is omitted) at the site where the pdrisechk command was executedYY
    6Whether or not the pair logical volume group in 4 above has the pair status shown in Table 2-30 List of pair statuses checked by the pdrisechk command at the site where the pdrisechk command was executedYY
    7Whether or not the pair logical volume group in 4 above has the fence level shown in Table 2-31 List of fence levels checked by the pdrisechk command.YY
    8Whether or not all status files for log application processing are in initial statusNY#2
    Legend:
    Y: Checked
    N: Not checked
    #1
    When the system switchover facility is employed in HiRDB and the pdrisechk command is executed in the secondary system, the site status is not checked because it cannot be identified. The KFPS04692-W message is displayed and processing resumes.
    #2
    The pair logical volume group to be checked is determined by the specification of the -d, -u, and -s options.

    Table 2-28 List of volume attributes checked by the pdrisechk command (when the -l option is specified)

    Pair logical volume group nameReal Time SAN Replication processing method
    All synchronous or hybrid methodAll asynchronous methodLog-only synchronous method
    -r option specified-r option omitted
    aaaa_bb....bb_DBS-VOL--S-VOLSMPL
    aaaa_bb....bb_LOGS-VOL
    aaaa_bb....bb_SPD
    aaaa_cccc_USTS
    aaaa_bb....bb_SSTS
    aaaa_ALL--S-VOL----
    Legend:
    aaaa: HiRDB identifier
    bb....bb: Server name
    cccc: Unit identifier
    --: Not applicable

    Table 2-29 List of volume attributes checked by the pdrisechk command (when the -l option is omitted)

    Pair logical volume group nameReal Time SAN Replication processing method
    All synchronous or hybrid methodAll asynchronous methodLog-only synchronous method
    -r option specified-r option omitted
    aaaa_bb....bb_DBP-VOL--P-VOLSMPL
    aaaa_bb....bb_LOGP-VOL
    aaaa_bb....bb_SPD
    aaaa_cccc_USTS
    aaaa_bb....bb_SSTS
    aaaa_ALL--P-VOL----
    Legend:
    aaaa: HiRDB identifier
    bb....bb: Server name
    cccc: Unit identifier
    --: Not applicable

    Table 2-30 List of pair statuses checked by the pdrisechk command

    Pair logical volume group nameReal Time SAN Replication processing method
    All synchronous or hybrid methodAll asynchronous methodLog-only synchronous method
    -r option specified-r option omitted
    aaaa_bb....bb_DBPAIR--PAIR--
    aaaa_bb....bb_LOGPAIR
    aaaa_bb....bb_SPD
    aaaa_cccc_USTS
    aaaa_bb....bb_SSTS
    aaaa_ALL--PAIR----
    Legend:
    aaaa: HiRDB identifier
    bb....bb: Server name
    cccc: Unit identifier
    --: Not applicable

    Table 2-31 List of fence levels checked by the pdrisechk command

    Pair logical volume group nameReal Time SAN Replication processing method#
    All synchronous methodHybrid methodLog-only synchronous method
    Protection mode =Protection mode =Protection mode =
    dataneverdataneverdatanever
    -r option specified-r option omitted-r option specified-r option omitted
    aaaa_bb....bb_DBdataneverasyncasyncdata--never--
    aaaa_bb....bb_LOGdatadatadatanever
    aaaa_bb....bb_SPD
    aaaa_cccc_USTS
    aaaa_bb....bb_SSTS
    Legend:
    aaaa: HiRDB identifier
    bb....bb: Server name
    cccc: Unit identifier
    --: Not applicable
    #: In the all asynchronous method, async is set for aaaa_ALL.
  8. The command checks whether or not the status file for log application processing is in initial status. Whether or not this checking takes place depends on the processing method of Real Time SAN Replication and whether or not the option is specified. The table below shows the conditions for checking the initial status of a status file for log application processing.

    Table 2-32 Conditions for checking the initial status of the status file for log application processing

    Real Time SAN Replication processing methodOption specificationChecking of status file for log application processing
    -d-l-r or -n-sStatus file for log application processing for unitStatus file for log application processing for server
    Log-only synchronous methodALL, SYS, or omittedSpecifiedSpecified--YY
    OmittedOmittedNN
    SpecifiedYN
    Omitted----YY
    DB------
    Other--------
    Legend:
    N: Not checked
    Y: Checked
    --: Not applicable

(6) Notes

  1. Return code 0 for the pdrisechk command indicates normal termination, and return code 8 indicates abnormal termination. When the return code is 8, see the previous message and eliminate the cause of the error.
  2. The result of the pdrisechk command is displayed in the KFPS05815-I message.
  3. Take the appropriate action indicated by the displayed error message and then re-execute the pdrisechk command until OK is displayed in the KFPS05815-I message as the command termination code (end code).
  4. Depending on the detected error, the command cancels checking at the point where the error is detected. A new error message may be displayed even after you have taken the appropriate action indicated in the displayed error message and then re-executed the command.
  5. For a HiRDB that uses a system switchover facility, the pdrisechk command always checks the configuration of Real Time SAN Replication based on the primary system's system definitions. Therefore, the result cannot be guaranteed if the pdrisechk command is executed while the running unit or server is not the primary system. During HiRDB operation, make sure that you execute the pdrisechk command while all running units and servers are the primary system.
  6. If the configuration to be checked contains a floating server, the command may display the KFPS01896-E and KFPS04680-E messages. You may ignore these messages. If you have checked only the pair logical volume group correspondence to the floating server, specify sys in the -d option.
  7. An error results if the -r option is specified when the log-only synchronous method is not used, or when the log-only synchronous method is used but the status is not log application.