We have a file of 3000 records. We can put a BTree index on a field on a stand-alone PC.

In a Novell Client Server/Win 95 environment, we can ADD the index but the index will not build. The REBUILD option will not build as well.

We have tried building the index on a stand-alone PC then moving the sub-directory of data on to the network and tried the REBUILD without success. Other BTree indexes work fine. We have logged into under SUPERVISOR.

Sometimes the Indexing will lock up the terminal. In other nothing happens.

Is there any reason why this one index does not work?

We are also suspicous that if there is more than 1GB of space free on the server disc can cause 'DISC FULL' messages. Anyone else have problems in this area?

If you are suspicious about the disk space thing, you might want to try one of the replacement dspace functions and see if that changes anything.

[email protected]

Sprezzatura, Inc.

James,

Have you tried manually removing the index (KB #56)? If not, and it's just this one index, I would go ahead and try that first, just to make sure the slate is clean.

Afterwards, make sure you are using Novell's Client32 (version 2.2 or 2.5 – please note if you are using 2.5, you will have to use the DOS login.exe or map.exe to either relogin or remap your OI drive. This is due to a bug in the driver; we are speaking with Novell about this). From your message, I take it you can build the index locally, which means the local-access mode of whatever driver you are using doesn't seem to have any gripes. Are you using the NLM for server access? If so, try logging everyone out of the system, change your driver to the All Networks driver, and then have one person (you) login and try to rebuild the index. If that works, but switching back to the NLM driver breaks it, there's an NLM issue which I'll have to switch brain modes to think about :)

If that's the case, make sure you're using the latest version (v1.5). Oh, one more thing, do you use a dedicated indexer?

-Scott

Revelation

In addition, always make sure your tables have RWSh attributes on. When removing indexes, ALWAYS make sure that no other users are on the system (including index servers) and that the index table is not locked.

We are running Novell Intranetware Client on NT and 95 boxes against a Novell 4.11 server. The problem we are running into is that all rows are not appearing in the GUI search window of the front end app when doing a display full table type of query. However, the rows will be retrieved if the record is directly queried in the search. ID#, Description, etc. Basically any valid column value will retrieve the row through a direct query, but not through an empty search. Most rows are retrieved. It seems to behave like a filter problem, but we think it may be related to the indexer.

Help!

How are you executing the query? How many rows are returning? You could be hitting a limit of the control's ability to display text or the retrivals limits.

[email protected]

Sprezzatura, Inc.

Regarding the DISC FULL messages. In the past, I have found these messages to be related to the Novell file ownership names. Typically, if a user name is dropped and they were listed by Novell as the owner of a file, Novell will not let any other user "extend" that file. To let you know it has a problem, Novell says the "DISK is FULL" which of course is not true.

You can fix the problem by resetting the file ownership names using FILER, when logged in as Admin or Supervisor. Set the entire directory structure to ADMIN or SUPERVISOR as the owner, since they are likely to not be deleted as users.

The only problem, is that any user that compresses a Rev file using DUMP will become the new "owner" of that file, so you have to reset the ownership periodically (or only allow ADMIN and SUPERVISOR to run DUMP).

View this thread on the forum...