Performs an integrity check on a GT.M database file. You can perform structural integrity checks on one or more regions in the current Global Directory without bringing down (suspending database updates) your application. However, a MUPIP INTEG on a single file database requires standalone access but does not need a Global Directory. The order in which the MUPIP INTEG command selects database regions is a function of file system layout and may vary as files are moved or created. Execute a MUPIP INTEG operations one database file at a time to generate an report where the output always lists database files in a predictable sequence. For example, to compare output with a reference file, run INTEG on one file at a time.
Always use MUPIP INTEG in the following conditions:
Periodically - to ensure ongoing integrity of the database(s); regular INTEGs help detect any integrity problems before they spread and extensively damage the database file.
After a crash - to ensure the database was not corrupted. (Note: When using before-image journaling, when the database is recovered from the journal file after a crash, an integ is not required).
When database errors are reported - to troubleshoot the problem.
The format of the INTEG command is:
I[NTEG] [ [-A[DJACENCY]=integer] [-BL[OCK]=hexa;block-number] [-BR[IEF]] [-FA[ST]] [-FU[LL]] [-[NO]K[EYRANGES]] [-[NO]MAP[=integer]] [-[NO]MAXK[EYSIZE][=integer]] [-R[EGION]] [-S[UBSCRIPT]=subscript] [-TN[_RESET]] [-[NO]TR[ANSACTION][=integer]] [-[NO]O[NLINE]]] [-FILE] file-name|-REGION region-name
MUPIP INTEG requires specification of either file(s) or region(s).
Press <CTRL-C> to stop MUPIP INTEG before the process completes.
The file-name identifies the database file for a MUPIP INTEG operation.The region-list identifies one or more regions that, in turn, identify database files through the current Global Directory.
MUPIP INTEG operation keeps track of the number of blocks that do not have the current block version during a non-fast integ (default or full) and matches this value against the blocks to upgrade counter in the file-header. It issues an error if the values are unmatched and corrects the count in the file header if there are no other integrity errors.
![[Important]](images/important.jpg)
Promptly analyze and fix all errors that MUPIP INTEG reports. Some errors may be benign while others may be a signs of corruption or compromised database integrity. If operations continue without fixes to serious errors, the following problems may occur:
Invalid application operation due to missing or incorrect data.
Process errors, including inappropriate indefinite looping, when a database access encounters an error.
Degrading application level consistency as a result of incomplete update sequences caused by the prior symptoms.
FIS strongly recommends fixing the following errors as soon as they are discovered:
Blocks incorrectly marked free - these may cause accelerating damage when processes make updates to any part of the database region.
Integrity errors in an index block - these may cause accelerating damage when processes make updates to that area of the database region using the faulty index. For more information, refer to Chapter 11: “Maintaining Database Integrity”.
MUPIP INTEG -FAST and the "regular" INTEG both report these errors (These qualifiers are described later in this section). Other database errors do not pose the threat of rapidly spreading problems in GDS files. After the GT.M database repair, assess the type of damage, the risk of continued operations, and the disruption in normal operation caused by the time spent repairing the database. For information on analyzing and correcting database errors, refer to Chapter 11: “Maintaining Database Integrity”. Contact your GT.M support channel for help assessing INTEG errors.
The following sections describe the qualifiers of the INTEG command.