Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 28 FEB 2007 08:48:03AM Sean Bartram wrote:

Using OI 7.1 on Windows Server 2003 Service Pack 1, with XP workstations - I've been developing in this environment for months with no problems. Yesterday, at midday (and since then) all OI programs (i.e. OpenEngine, App Manager, Database Manager, System Editor, etc.) shut down completely at random - there is no rhyme or reason to when it shuts down. Sometimes it's as soon as you log into the application, others you can be working along for several minutes, then poof - gone. It seems to only happen when the client side is idle. I've even tried running locally on the server itself, (to eliminate the network as an issue) with the same results. I was able to run the OI Examples app on the server without this problem occurring.

There were no changes on the server or workstations yesterday, although I was developing in the application, I cannot imagine why something in the app would cause this random shutdown of OI. Any thoughts or suggestions would be greatly appreciated.


At 28 FEB 2007 08:55AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:

If you are running UD3 move back to 2.1 and review

http://www.sprezzatura.com/senl/volume_4_issue_3.htm#DEP

The Sprezzatura Group

World leaders in all things RevSoft


At 28 FEB 2007 09:19AM Sean Bartram wrote:

We have never switched to UD3 - using 2.1


At 28 FEB 2007 01:12PM Bob Carten wrote:

In database manager, Environment settings - is background indexing set to run every 5 seconds? Try extending to 30+ seconds, see if that helps.


At 28 FEB 2007 02:19PM Sean Bartram wrote:

I increased the time of the background indexing to 60 seconds, after a little over a minute - poof, OI closed. I changed it back to 5 seconds, within 15 seconds of being idle - poof.

So perhaps there is an index somewhere that is abending? Is my only recourse to go and rebuild all the indexes in the system?


At 28 FEB 2007 02:30PM Sean Bartram wrote:

Of course, when I attempt to rebuild any and all indexes in a suspect table, OI abends.


At 28 FEB 2007 03:07PM Sean Bartram wrote:

I've also tried removing the suspect files indexes, with the same result - abend.


At 05 MAR 2007 04:18AM [email protected] wrote:

You'll probably need to rebuild the indexes manually. Although this document is for ARev, the basic concepts are the same. If you need some help in finding the comparable OI commands, let us know.

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft


At 05 MAR 2007 09:50AM John Bouley wrote:

I would add you should do a verify first. Also, OI index rebuild is not really great in handling/reporting errors.

We just recently had a customer report a problem of not being able to lookup data. The OI indexer blistfully flushed indexes with no indication of a problem while AREV reported that the link list was corrupted and needed to be rebuilt. When we tried rebuilding in OI it "flashed" and reported the rebuild was complete eventhough nothing happended. We had to delete the queued records before OI could rebuild.

I'm looking forward to testing this in 8.0…

HTH,

John


At 13 MAR 2007 08:21AM Sean Bartram wrote:

Bob,

That was indeed the problem, thank you for your insight. Once I knew it was an index I was able to remove the index and rebuild from scratch.

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/81fffe98dab6182a85257290004bcfbb.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1