Ingress running like a dog!

[Mike Laytham_1]

Has the patch fixed the problem, as we are still in dispute with CA as to who's issue our problem resides with... OS or Ingres..

If you could supply some more information on what happens it would be appreciated.

thanks

Mike

[Chris Wilshaw]

Mike,

So far, we've had no problems on the patched systems.

The issues that we had were;

1) "spinning" DBMS server. Some unknown process attaches to the dbms server, causing it to take up as much CPU as possible. Once this happens, no other processes are able to connect to the server (sql, ipm etc all just hang). The only solution here is to kill off all application processes, then try to shut ingres down. Most of the time this works, although occasionally, you have to kill off a couple of the ingres processes too.

2) query flattening problem. This is supposedly due to an SQL routine picking up an inefficient query plan when it runs. When this happens, other processes can connect to the server, but everything takes a long time to run. Once the initial query ends (or is killed), the server state returns to normal. This sounds like it fits your problem.

The spinning server was our main problem (we were getting one of those a week on average). We only had 2 instances of the query flattening problem, and they were fixed by the application developers by setting (I think) trace points within the code to force the choice of query plan.