HR-1 Error Message (AREV Specific)
At 22 MAR 2000 09:38:25AM Matt Sorrell wrote:
I'm stumped on a problem in our development environment, and I'm hoping somebody remembers HR-1 fairly well.
Here's the skinny:
I have a table that stores health insurance information, name COBRA.
I am attempting to update a value for a record in this table, and I get a B441 error message: "Records cannot be updated because the table 'TEST_EMP' is not available or attached for reference to store index transactions. Please attach this table and try again."
The table TEST_EMP does exist and is attached at startup.
The COBRA table, which I'm trying to update, has 2 MFSs attached; AUDITLOG.MFS and SI.MFS. The field that I am trying to update is not an indexed field, so I don't know why it needs to store index transactions. To my knowledge, this field is not part of a relational index in another table.
I have tried completely rebuilding the indexes on the COBRA table, I have deleted and recreated the TEST_EMP table, and I've begun plucking my eyebrows to see if some archaic mystical rite might help (it doesn't, and it hurts like the dickens).
I have checked any triggers and audit groups defined on the table, and none of them reference the field I'm updating, and none of the subroutines call TEMP_EMP.
I'm at a complete stand-still here. Funny thing is, it only happens in our development environment, and only on this one table. Something is very much weird…
Any help would be greatly appreciated!!!
Matt Sorrell
msorrel@greyhound.com
At 22 MAR 2000 10:00AM Matt Sorrell wrote:
Never mind. It was a corrupted index. I completely removed the indexing, and then re-added my indexes and everything works fine now.
Sorry to waste your time.
Matt Sorrell
msorrel@greyhound.com
At 22 MAR 2000 10:00AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
Does the volumne name in the !filename row in the !filename actually match the proper volumn name?
World Leaders in all things RevSoft
At 22 MAR 2000 10:22AM Matt Sorrell wrote:
It's fixed now. I had to completely remove and rebuild the indexes. They got thrashed somehow.
The answer was staring me in the face, I just didn't recognize the error message for what it was.
Matt
At 22 MAR 2000 04:50PM Steve Smith wrote:
Matt -
Another possibility - could it have been that the MFSs were applied in the wrong sequence, and removing them then reinstalling them left the
MFSs in the correct sequence?
Steve