Dest. media label written on source revmedia (AREV Specific)
At 04 FEB 1998 05:05:14PM Victor Engel wrote:
A coworker of mine just attempted to do a table copy from one volume to the other. The table did not already exist on the destination volume. In effect, he was making a backup of the file. After the copy completed, users began complaining that the system would not let them save records, that they had to reattach the file, and also:
RECORDS CANNOT BE UPDATED BECAUSE THE TABLE !EMP IS NOT ATTACHED FOR REFERENCE TO STORE INDEX TRANSACTION ERR: B441
I edited !EMP !EMP and compared to REVMEDIA REVMEDIA and voila! They were not the same. I then checked the REVMEDIA record on the destination volume (C:\LOCAL), and it DID match !EMP !EMP. It seems that the table copy corrupted the index transaction record on the source volume.
Suspecting some further activity, I checked the command stack. The only things after the the table copy were ATTACH REVBOOT and logging off, following by logging back on.
The Arev version is 3.02 (HR-1 5.50). Any idea what happened?
At 05 FEB 1998 11:16AM Victor Engel wrote:
Can someone who knows post a description of exactly what happens in the table copy in the order that it is done? I would like to know things like.
* When each file is attached/detached (including REVMEDIA files, dictionaries and indexes)
* What locks are set
* How indexes are handled
* What action is taken if the dictionary/index file is (are) missing
* Do command line options change any of the above
I'm thinking that what may have happened is that in the sequence of events, the local (destination) file already existed, but without any indexes. The system, seeing that the data file already exists doesn't create a new one. When it gets around to synching the indexes, there is no destination index file, so the source file is updated with destination information. Is this a likely scenario?
Victor