Index problems and NLM (AREV Specific)
At 28 JAN 2000 07:36:10AM Claude Mansutti wrote:
I have a site running Arev 3.12 on a Novell 3.2 Network with the Arev NLM and a seperate indexer. Their server was replaced just before the start of this year and since then they have been getting indexing problems. If it makes a difference, the new server is using NLM Ver 1.04 where the old server had Ver 1.02.
Their latest crash has been a link list error on the index of their main table of some 300,000 records. I removed all the indexes (10 in total) and rebuilt the "SURNAME" index. The result was only names from A to L being available via indexing, M-Z don't seem to exist. A retry at rebuilding, got all the way to "Simpson" (appropriate huh) so what is causing it to stop? I read through earlier threads before writing this, and found exactly the same problem for someone back in 1997. However, there wasn't any clear answer or resultant success note.
Also, even if I remove all the indexes, it doesnt remove DICT.TableName. If I manually delete Dict.TableName and set row 6 in the dictionary to null for all the indexed fields, it wont let me edit the TableName because !TableName is missing. Am I missing something? Is a little knowledge a dangerous thing when playing with indexes?
Any suggestions?
TIA Claude
At 28 JAN 2000 08:27AM Mike Ruane, WinWin Solutions Inc. wrote:
Claude-
Have you checked the REVMEDIA entry for your table, after you remove all indexes, and looked for the SI.MFS in the record?
If you've removed all indexes, SI.MFS should no longer appear in the send field on the REVMEDIA record. If it is in there, remove it.
Also, after you remove all indexes from a table, try and remove the table from the application, log out of OI, log back in, and re-attach the table. This sometimes helps.
Hope It Helps-
Mike Ruane
WinWin Solutions Inc
WWW.WinWinSol.Com
At 28 JAN 2000 10:24AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
If he was using OI he might also want to check the DBT. Fortunately he did state that he was using AREV so he's saved that chore.
You might want to try rebuilding locally without the NLM to see if it's a server/net problem.
World Leaders in all things RevSoft
At 28 JAN 2000 10:53AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Additionally, and we cannot recommend this strongly enough…
UPGRADE OFF THE 1.04 NLM!
(if you check out the HTML code, you'll see we felt so strong, we used the strong tag…)
There were serious flaws in older versions of the NLM. 1.5 is very stable product and any customer who has not upgraded to version 1.5 should contact Revelation right now and order your upgrades.
Some of the flaws in the earlier versions are serious enough to cause your problem. The select bug someone keeps harping about is potentially in older NLMs. That bug should have been fixed by the 1.06 NLM, 1.10 at the latest. While we are not 100% convinced that this is the source of your particular index problem, the affects of the bug could cause the effects you are seeing.
[/i]World leaders in all things RevSoft[/i]
At 28 JAN 2000 11:41AM Claude Mansutti wrote:
Thanks for the info.
I personally thought it would be risky going from what was a relatively stable NLM Ver1.02 to the unknown Ver1.04 . I should rely on my gut instincts more. In the meantime can I downgrade to ver 1.02?
Thanks for taking your time to add HTML code
Claude