HP Integrity NonStop H-Series Guide de l'utilisateur télécharger pdf (Page 212)

HP NonStop Shadowbase Command Definitions

Database Specification Command Descriptions

HP NonStop Shadowbase Command Reference Manual—785421-002

203

BRIEF – By default, there are two sections of reporting. The detailed part

will show the source/target file list and any potential issues associated with

the mapping between them. At the end, there is a summary list which

shows different categories of issues and other count information about

files selected and found, etc. The BRIEF option will only show the

summary lines. Note that the CONS still executes the logic to locate

sources and targets and performs the checking associated with “check

targets”. The amount of detailed output can be much greater than the

summary output, which is typically less than a page.

FIRSTFOUND – This option will produce a detail and summary section.

However, only the first source file found for a given DBS SOURCEFILE

will be reported. This can reduce the “check targets” run time. However,

it is possible that some potential issues could go undetected and

unreported (e.g., target for a particular source file is missing, more than

one logical table/file could be picked up based upon the SOURCEFILE

and you only desired a certain table/file and its partitions, etc.). If you use

this option, you should also manually check the list of sources and targets

that are associated with your DBS object.

MSGLINES – This option will produce a detail and summary section.

However, only the first source/target lines that have potential issues are

reported. Those that went through the checking without incident are not

reported.

“Check targets” can also optionally verify that the data types for common

columns (same column name in the source and target) are the same.

VERIFYSCHEMA – This option will cause the CONS to also compare

schema data types between a source file/table and related target file/table

and report on any different in the “xxxCHK” report.

Note: At this time in almost all cases with NSK-to-NSK replication, that

the target data type MUST match the source data type. Different

data types can cause the Consumer to trap. In some cases, this

can occur within the HP SQL executor code without any EMS

messages to indicate that the data is incorrect.

It is a good idea to use the VERIFYSCHEMA option on the CHECK

command for new DBS objects in order to verify compatibility between a

source file and target file. Note that, even if a user exit is associated with

a DBS object, the report will show data type differences with a note that

there is a user exit.

1 2 ... 207 208 209 210 211 212 213 214 215 216 217 ... 345 346

Pas de commentaire

HP Integrity NonStop H-Series Guide de l'utilisateur Page 212