missign tables and indexing (OpenInsight 32-bit Specific)
At 11 MAY 2007 11:28:50AM Mike O'Neal wrote:
Hello all -
I am trying to install new btree and relational indexes on a table that already has both of these types of indexes installed. I cannot see *any* tables though when I attempt to add these via database manager - the dropdown for the table name is not functional. Environment is OI 7.2.1, UD 3.0.0.3 running locally with the revparam disabled. (Normally this on a network but I have copied to a local drive to diagnose)
1) I can see the table via system editor and I can run r/list statements against it
2) I can open the !file, all appears normal (at least as far as I can tell)
3) I have verified that there are no GFE's.
4) LIST_INDEX and LIST_TABLES runs fine via system monitor.
5) I can remove an index via database manager with no problem
6) I have created a new .dbt by re-naming SYSPROG.DBT and then using database manager to attach the appropriate folders, but I am now getting B441 messages (I was not getting these before)
(Thanks to Bob C. for all of the above suggestions)
Any ideas as to why I cannot install a new index?
TIA, Mike O.
At 12 MAY 2007 02:27PM John Godfrey wrote:
Use below at your own risk (Backup Tables first) but I have done the following to solve this frequent problem.
Try removing all the indexes in a table then the !table using a 'delete_table' command from an exec line. Add a Btree index to wake up the table then reinstall indexes.
At 13 MAY 2007 10:46AM Richard Hunt wrote:
"B" series error messages, I believe, are from the RBASIC compiler. If you mean an "FS441" then I think that has to do with the sorting of a select list. Maybe the temp file that the system uses for sorting is invalid?
What is the actual "B441" error message?
At 14 MAY 2007 04:44PM Bob Orsini wrote:
* B441 Records can not be updated because the table "%1%" is not available or attached for reference to store index transactions.
At 27 MAY 2007 05:21AM John Godfrey wrote:
I've had this problem myself now. I attach and reattach between a 'Live' & 'Demo' area. Database Manager seems to get out of synch with what is actually attached, so had to run ATTACH_TABLE from System Monitor to ensure the !File was properly attached. Database Mgr was showing everything to be attached properly even though it wasn't. Once correctly attached CLEAR_TABLE was then used to free a logjam in the !File and allow indexing again. Database Manager seduces you into entering a path when you should be entering a volume name. If both path and name used casually, everything gets confused. Especially me. Now working OK but hope the above may give some ideas to annyone else who encounters this.
At 31 MAY 2007 04:07PM Mike O'Neal wrote:
Hi John -
It turns out the problem I had was a corrupted DICT.SYSVOLUMES table. Once that was fixed I was able to at least see my tables again. I still have stalled indexes though (rebuilding does not update the indexes) so I am intrigued by your CLEAR_TABLE statement. Could you explain why you needed to do this?
TIA, Mike O.