server file open error (AREV Specific)
At 14 JUN 1999 02:02:31PM Aiden Massey wrote:
HELP!
5 users with nothing to do, critical table not avaialbe.
Could not access data table, problems with index table. Deleted indexes manually.
Arev 3.2
Novell 4.11
Nlm
The !PRINCIPAL_CUSTOMER table is not available
Linear Hash Client/Serve
Server file open error
File name "COVDATA\REV64155. ".
COVDATA\ does not exist, should be CMGDATA. rev4155.lk rev64155.ov still exist at CMGDATA\.
This sytem has been stable for 2+ years.
At 14 JUN 1999 02:38PM [email protected] wrote:
Problem might be that ARev 3.2 is notoriously unstable. Try upgrading to ARev 4.
At 14 JUN 1999 02:46PM Aiden Massey wrote:
What about Arev 5?
At 14 JUN 1999 03:31PM Victor Engel wrote:
Actually, go for Arev 2000 (assuming you have enough disk space).
Seriously, though, I encounter a problem similar to this on occasion. The most common symptom is that one or mor characters in the file name are transposed into something else. Most consistent is the E changing to O in REV#####. Then the extention gets garbled a bit. I don't have an explanation for why this happens. But I do know that it happens during backups. Our normal backups happen after 11PM, and if our downloads continue past this time, we are likely to get such errors. One time, we got these errors in the middle of the day. A quick phone call to the data center verified that a mid-day backup was in progress.
At 14 JUN 1999 04:08PM Aiden Massey wrote:
Also suspicious tape backup might have caused problem (tape software on server had to be reloaded).
How did you fix problem?
At 14 JUN 1999 04:37PM Victor Engel wrote:
Deny logons during backups. We are looking at changing backup software.
At 14 JUN 1999 05:35PM Aiden Massey wrote:
Appears to be NLM problem. No problem accessing index table from Sysprog, no NLM.
arev sysprog /x (no lhipxtsr)
setalias cmgdata contact principal_customer sysalias
dumplh !sysalias (definitely principal_customer index table)
Cheers
Aiden
At 14 JUN 1999 10:54PM Aiden Massey wrote:
Not sure which change fixed the problem
table PRINCIPAL_CUSTOMER
1. removed quickdex (dict)
2. DELETEROW DICT.PRINCIPAL_CUSTOMER %PROTECT.SPEC%
3. DELETEROW DICT.PRINCIPAL_CUSTOMER %FIELDS%
table !PRINCIPAL_CUSTOMER
from SYSPROG
4. ATTACHTABLE CMGDATA REVMEDIA
5. DELETEROW REVMEDIA !PRINCIPAL_CUSTOMER
reinstalled indexing on PRINCIPAL_CUSTOMER, life is perfect!