'Secondary Indexing Involved' (AREV Specific) [Revelation On-Line Wiki]

Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 03 DEC 1997 11:59:15PM Christine wrote:

AREV Specific

Often when we move a sub-directory of data from

a network to a PC we get the message:
  The media map says the file is involved in
  Secondary Indexing ......
We would like to write a program to remove this

flag so that we can use the file. Does anyone

know the key commands required to achieve this.

At 04 DEC 1997 08:49AM Aaron Kaplan wrote:

I don't think I've ever seen this error, at least phrased the way you've indicated.

The indexing system stores volume pointer information so it can always identify the correct files, even if they are aliased in.

If you're just copying subdirectories whole, then there should not be a problem.

If you could post the full error message, including number, it would be helpfull.

[email protected]

Sprezzatura Ltd

At 05 DEC 1997 12:24PM Victor Engel wrote:

I suspect that what you are running into is a conflict with volume labels. When you create a volume in Arev, a volume label is created in the REVMEDIA record of the REVMEDIA file. This label is used in the construction of indexing records.

When the indexing PC encounters index transaction, this volume pointer is used to ensure that the correct file is being updated. This scheme is used to guarantee that a particular volume/file combination is being used. This is an issue, because the same file can be attached different ways (through a volume name set up in Arev, using the DOS path to the director more than one path could potentially lead to the same directory)

Now what you are doing is copying a volume to a different location. However, the volume label remains the same. Arev has a checkto make sure you don't do this. If you attach a volume that has a label that already exists in one of the already attached volumes, you will get a message indicating the conflict. There are a couple of solutions to this:

1) Detach one volume before attaching the other volume. It is not sufficient to detach just the file you're working with. You must detach the entire volume.

2) Rename the volume label on one of the directories. Do this with the NAMEVOLUME command. You must remove all indexing on the label before renaming.

At 06 DEC 1997 12:52AM Mark Martin wrote:

Hi Aaron,

It sounds like they are FILECOPYing the files and one of them has a relational index on it.

View this thread on the forum...