Document Type | Troubleshooting
Category | Utility
Applicable Product Version | 6FS06
Document Number | TUTTS007
Issue
- tblogdump, tbhdreditor, tbdv and other analysis tools cannot directly access TAS.
- When attempting to dump only specific blocks using tblogdump, it takes an unusually long time.
Cause
- In some versions, there was an issue with the API used to access TAS, causing these tools to be unable to access TAS files.
- When running tblogdump and attempting to dump only specific blocks, the internal logic also dumps the dfhdr block, which results in delayed operation times.
Solutions
Solutions by Tool
- tblogdump: Check the dump contents of Redo and Archivelog.
- tbhdreditor: Extract header information of data files.
- tbdv: Verify data file integrity.
CautionIt is recommended to use the latest client tools.
Usage
- Example of TAS Access Method
$ ./tbdv -m 1024 +DS0/system001.tdf:localhost:38100
- When using tblogdump, example of dumping only specific blocks
$ ./tblogdump -a 669_00000759 +RECO01/DGDWP01/archive/arch_DGDWP01_4_15485_0.arc:localhost:38100
- When using tblogdump, example of dumping specific blocks including dfhdr
$ ./tblogdump -a 669_00000759 --blkhdr +RECO01/DGDWP01/archive/arch_DGDWP01_4_15485_0.arc:localhost:3810