The hrnbrptr utility validates the integrity of page images in either an archive file or a database segment by validating the horizontal and vertical pointers within the file specified. Run this utility on a regular basis against your TIBCO Object Service Broker system backups or segments to guarantee that every referenced page is accessible.
The filename argument can be one of the following:
The dbdef specification for the requested segment does not require the OS_ROOT environment variable to be set as long as the dbdef DB PATH option is used with or without FILE statements. The access path to a segment file is determined by the following: 1) the dbdef FILE statement, if specified, 2) the DB PATH option, if specified, and 3) the
OS_ROOT environment variable.
|
|
|
|
|
|
|
|
|
|
|
The file to which the error log is written. If this argument is omitted, the report is written to ERRLOG.ptr in the current directory.
|
|
|
The number of errors and warnings permitted before hrnbrptr quits. The default is 1000. A value of 0 (zero) permits an unlimited number of errors and warnings.
Note If your archive file or segment has many problems, this setting could produce very large audit report and error log files.
|
|
|
Print the page headers. This argument must precede the -H argument. If -H is not specified, the headers are written to PGHDR.ptr in the current directory.
|
|
|
The file to which the page headers are written. If this argument is omitted and the -h argument is specified, the headers are written to PGHDR.ptr in the current directory. This argument has no effect unless -h is also specified.
|
|
|
|
|
|
The file to which the orphan log is written. If this argument is omitted, the log is written to ORPHAN.ptr in the current directory.
|
|
|
The hrnbrptr utility automatically assigns a buffer of 200,000 pages for the Pagestore. Use this argument to set a higher number of pages if necessary.
|
|
|
The file to which the reference log is written. If this argument is omitted, the reference log is written to REFLOG.ptr in the current directory.
|
|
|
The offline segment number (not segment name). If this argument is omitted, the segment number defaults to zero (that is, the MetaStor is assumed).
|
|
|
|
|
|
The path of either the archive file created by the hrntlbps (Backup Pagestore) utility or a properly formatted dbdef file, which it recognizes by the .dbdef extension. For more detail, refer to Input.
|
Provides information on each of the tables that exist in the segment, each error condition found, plus a number of summary items. It contains important information for tracing problems and should be retained. For more information, refer to
Sample Audit Report.
Lists error messages detected by the validation process. It provides an easy reference to help you determine if errors exist. All messages are also reported in the audit log.
This file can be used as input to the hrnbrpgc (Pagestore Correction) utility. hrnbrptr extracts the timestamp from page 1 and puts it in the ERRLOG in the form
ID=xxxxxxxxxxxxxxxx. hrnbrpgc checks this timestamp against the then current page 1 before acting on an orphan-recovery request. If there is no
ID=line in ERRLOG or if the stamps do not match, the job aborts. If, after checking that the ERRLOG is still valid against the indicated segment, you decide to proceed with the recovery, either insert the following line after the headings in the ERRLOG file, or modify the existing
ID= line, as appropriate:
ID=IGNORE.
Contains a list of pages where the system usage indicators did not agree with reference information detected by Pointer Check processing. Orphans
do not appear as errors in the error count.
An orphan page is a page that is not available for use and is not referenced by a table. A page that is referenced by a table but is available for use is reported as REFERENCED BUT INDICATED FREE.
In the orphan file, the ORPHAN pages are listed with the previous and next page pointers as well as the page type. REFERENCED BUT INDICATED FREE pages are listed as a page number followed by the message text.
The reference log lists each referenced page in the segment. The log identifies the table, forward and backward chain pointers, and parent information. This information helps to identify how the page fits in the Pagestore.
A non-recoverable error results in an abnormal termination. Refer to TIBCO Object Service Broker Messages With Identifiers for messages issued by this utility.
