The onlog utility uses the pathnames that are stored in the root dbspace reserved pages to locate the logical-log files. If you use ON–Bar to back up the logical logs, onlog asks the storage manager to retrieve the appropriate logical-log records from the backup media.
Log-Record Read Filters: |--+----------------------+-------------------------------------> '- -d--device--+-----+-' '- -b-' .----------------------------------------------. V | >----+------------------------------------------+-+-------------| '- -n--starting uniqid-- ---ending uniquid-'
| Element | Purpose | Key Considerations |
|---|---|---|
| -b | Displays logical-log records associated with blobspace blobpages | Additional Information: The database server stores these records on the logical-log backup media as part of blobspace logging. |
| -d device | Names the pathname of the storage device where the desired logical-log backup is mounted | Restriction: If you use ontape, the device that you name must be the same as the pathname of
the device assigned to the configuration parameter LTAPEDEV. If the -d option is not used, onlog reads the logical-log
files stored on disk, starting with the logical-log file with the lowest logid.
Additional Information: You do not need to use the -d option if you use ON–Bar because the storage manager retrieves the logical-log records from the storage device. References: For pathname syntax, see your operating-system documentation. |
| -n starting uniqid-ending uniqid | Directs onlog to read all the logical-log records contained in the log file that you specified from starting uniqid to the ending uniqid. |
Additional Information: The starting uniqid and the ending uniqid are the unique ID numbers of the logical log. To determine the uniqid of a particular logical-log file, use the onstat -l command. If you do not use the -n option, onlog reads all the logical-log files that are available (either on disk or on tape). References: For information about the onstat utility, see Monitor the Database Server Status. |