G
George Potemkin
Guest
> without being able to run dbanalys or tabanalys we can't know for certain. You can find a point of tabanalys' failure: Start database in multi-user mode but don't allow for the users to connect to your db. Run tabnalys against the area where you got the errors. Use _ActIOFile._IOFile-Reads and _TableStat._TableStat-OsRead to check how many blocks in the specified area were read by tabanalys. Note that dbanalys/tabanalys do not change the record read statistics (_TableStat-read). _IOFile-Reads will give you an offset in the area to dump the record block contents using dbrpr. Dump a few blocks before and after the offset - just in case. If it's a storage area type 2 then you can use 4GL query with non-index scan. Check all records when your query creates the same _TableStat-OsRead as tabanalys before failure. Of course, you need to restart db to refresh its buffer pool.
Continue reading...
Continue reading...