Is this a possibility? (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|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]]


==== Is this a possibility? (AREV Specific) ====
=== At 28 AUG 2003 04:07:50PM Matt Sorrell wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
Okay, returning to the chronicles of my random GFEs, which have continued.  They almost always occur after work hours on the !EMP table.  This table is the one that is hit the hardest during the day since it is the primary data table.



We do have a dedicated indexer which also functions as a job scheduler thanks to a post-index process hook.  This machine stays up until approximately 2000 every evening, and is back up by 0100.  The downtime window is for backups.  I have verified that the dedicated indexer has been down during backups, so that's not the concern.



My thought, though, is this.  It was brought to my attention today that we were down to Greyhound Lines, Inc.[/url]
</QUOTE>
----

=== At 28 AUG 2003 05:08PM Pat McNerthney wrote:  ===

<QUOTE>Matt,



Do you have any processes run after hours that might be accessing the Linear Hash files and causing a conflict with the NLM?  Examples might be backups or virus scanners.



Pat

</QUOTE>

----

=== At 28 AUG 2003 05:25PM Matt Sorrell wrote:  ===

<QUOTE>Pat,



The only thing would be the backup, but it is scheduled for 2200 and runs in ~10 minutes, and we bring the indexer down at 2000 and don't bring it back up until 0100.



I've gone back over the logs for the last three weeks and the indexer was never up during the backups.



msorrel@greyhound.com

[url=http://www.greyhound.com]Greyhound Lines, Inc.[/url]

</QUOTE>

----

=== At 31 AUG 2003 04:12AM Steve Smith wrote:  ===

<QUOTE>Out of disk space conditions could trigger indexing GFEs - this is one error I don't think is checked very frequently. 



I'm certain Pat will correct me on this. (Pat - V119 uses temp files for its sort queues if I recall - could these pop available disk limits?) 



The other possibility is temp files clagging up the hidden \deleted.sav path on the SYS volume (where salvage.exe gets its files from under Novell) 



Another possibility is a disk limit set on the INDEXER user account (check Network accounting options).



Have you run FIXVOL.EXE and FIXGCE.EXE? 



Are all network drivers the same? 



Brownout? 



Bad battery on UPS? 



Bad network card?



Nasty case of virus interruptus?



A smoke and a pancake?



A cigar and a waffle?



A pipe and a crepe?



Then, sir, there is no pleasing you.... ;-)



Steve

</QUOTE>

----

=== At 04 SEP 2003 03:38PM Matt Sorrell wrote:  ===

<QUOTE>Steve,



Thanks for the info.



After we cleared up the disk space issue, low and behold we have not had any other problems.



I definitely think that was it.



Thanks!!



msorrel@greyhound.com

[url=http://www.greyhound.com]Greyhound Lines, Inc[/url]

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=CE51363BEBC9FE0E85256D90006E94D9|View this thread on the  forum...]]