Dropping views from the ii_database partition

Configuration: Ingres 6.4/02 (ds3.ulx/00) ULTRIX V4.4 (Rev. 69) on DEC 5500

We have a problem (apparently set off by the ii_database disk partition
filling up) with views that cannot be destroyed. Attempting to drop one
view generates a "E_RD0060_DMT_SHOW_ERROR/E_DM0075_BAD_ATTRIBUTE_ENTRY"
error; attempting to drop another never finishes and appears to lock 
iiattributes/iicolumns so that any other applications which access 
iiatt./iicol. will freeze waiting for the lock to release. The only way
to get rid of the latter process is to kill all the Ingres processes via
Unix and restart the database. With actual database tables that have 
generated similar errors we have been able to use the 'drop_table'
option of the verifydb command to eliminate them, but this does not
work with these views:

verifydb -mreport -sdbn "mel" -odrop_table "tmp_lkg3" -uakasten
>    *************************************************
>    verifydb
>     9-Nov-1995 13:42:32
>    *************************************************
>S_DU04C4_DROPPING_TABLE VERIFYDB: beginning the drop of table
> tmp_lkg3 from database mel.
>E_DU501B_CANT_CONNECT_AS_USER
>Unable to connect with database mel
> as user akasten.
>E_DU5024_TBL_DROP_ERR
>Unable to destroy table
> tmp_lkg3 from database mel.


Trying to use the -odbms_catalogs option to verifydb cranks along merrily
for awhile, "fixing" scads of "S_DU1611_NO_PROTECTS" errors and claiming 
to clear some bad views with "S_DU030C_CLEAR_VBASE" messages, but it even-
tually just hangs and has to be killed via 'ipm' without ever reaching the
bogus views. When killed it says was killed due log file full/force abort or
some other such nonsense.
 
All the records in the table the views are defined on are readable, 
the view definition itself is visible via 'help view ...' and the rows in
iirelation and iiqrytext corresponding to the views can be read and viewed. 
Copying our (huge) iiattribute table over to a 'recovery' database and 
running it through verifydb generates no bad data pages. The only thing
we can't do is try to select from the 'iiattribute' table using the
reltid, reltidx from the 'iirelation' table for these views and have it
return 0 rows; that select just hangs for both views.

At this point the only solution I see to try is to shutdown the production
database, copy the iirelation and iiqrytext tables over to a recovery
database, delete the rows corresponding to these views, and copy them
back over the original database catalogs. I would hope there is a better
solution out there.

Any help appreciated, thanks.

-- 
Greg Garland - Alive, occupying space, and exerting gravitational force
MS 62-024, Harris Semiconductor Sector, PO Bx 883, 
Melbourne  FL 32905.  geg@beep.mis.semi.harris.com
"Never let the facts interfere with your perception of reality."
Ingres Q & A
To William's Home Page
Email William