Re: archecker question

Chris Salch wrote:
> HPUX 11i IDS 9.40.HC5
> 
> I'm seeing this message in an archecker log file.
> 
> STATUS: Checking carstrain:syssyntable
> STATUS: Checking 0x00200B89:
> ERROR: bad extent number 0 -- only 0 extents.
> ERROR: Unable to convert logical address to physical address.
> STATUS: Checking 0x00200B8A:
> ERROR: bad extent number 0 -- only 0 extents.
> ERROR: Unable to convert logical address to physical address.
> 
> A google search reveals a reference to a bug fixed in version 10.xx
> 
> bug_number      172181
> description     ARCHECKER RETURNS MISLEADING ERROR MESSAGE LIKE "ERROR:
BAD EXTENT NUMBER 0 -- ONLY 0 EXTENTS." WITH IN-PLACE ALTER TABLE
PARTITION PAGES
> product_code    ONLINE
> component_code  ARCHECKR
> 
> Does this look like what I'm seeing here?  Is there a way to fix
whatever archecker thinks is wrong as upgrading right now is not really an
option.
> 
Get rid of the in-place alters.

i.e. run oncheck -pT 0x200B8a to see what table, and then do (IIRC) :

update table tab1 set (irrelevant column) = (irrelevant column) where 1=1;

Obviously beware of long transactions etc. etc.

If in doubt post the oncheck -pT output for the two tables.

And ... certainly looks like the bug.