> >
> > These are the number of connect(Login), disconnect(Logout) and
> > transactions.
> > As you can see they are connecting/disconnection some 1700+ times each
> > minute duing the entire day.
>
> No - they're just using a lot of transactions. Login and logout match
> your comparative data below. Autocommit mode would easily account for
> the higher number of transactions.

This might be true, but along this we have had some meetings where I had told them that I would have them to START and COMMIT every transaction manually.
In my experience this works way better than autocommit.

Anyway
Whatever kind of connection they have and whatever they use it for they do connect/disconnect more than 1700 times per minute.
None of hour programs whatsoever comes this high.

They have had a connection fore some month.
The first 2½ month there where no problems. And they had a 20-80 connect/disconnect per minute. I still find this to be a lot given what they do, but it worked.

Then suddenly this rose to 1700+. And the server started to die.
I contacted them, and for a week they disabled one thing, and the connect/disconnect went dowen to 20-80.
And the problem disappeared.
NOw the day before yesterday they enabled again, and I started to die again.

My logical conclussion is that this is causing the problem.
It runs smoothly without this. It dies with this.

>
> > DWIUSER Commit Trans 6/6/2012 32384 22.48
> > DWIUSER Start Trans 6/6/2012 18054 12.53
> > DWIUSER Commit Trans 6/7/2012 8297 5.761
> > DWIUSER Start Trans 6/7/2012 4347 3.018
> > ESCONSERVICE Commit Trans 6/6/2012 607 0.421
> > ESCONSERVICE Login 6/6/2012 286 0.198
> > ESCONSERVICE Logout 6/6/2012 286 0.198
> > ESCONSERVICE Start Trans 6/6/2012 607 0.421
> > ESCONSERVICE Commit Trans 6/7/2012 171 0.118
> > ESCONSERVICE Login 6/7/2012 79 0.054
> > ESCONSERVICE Logout 6/7/2012 79 0.054
> > ESCONSERVICE Start Trans 6/7/2012 171 0.118
> >
> >
> > This morning (and some 10-12 times more the last 3-4 days) the server
> > died with this:
> >
> > DBSRV03 (Server) Thu Jun 07 06:06:02 2012
> > Database: ThreadData::start() failed:
> > operating system directive _beginthreadex failed
> > Not enough storage is available to process this command.
> >
> > Which I believe is "out of memory" problem.
>
> It rather sounds like "disk full", but I believe you're correct:
>
> http://technet.microsoft.com/en-us/library/cc978735.aspx
>
> User Action:
> Do one of the following, then retry the command: (1) reduce the number
> of running programs; (2) remove unwanted files from the disk the
> paging file is on and restart the system; (3) check the paging file
> disk for an I/O error; or (4) install additional memory in your
> system.

Disc is not full.
OS in is drive C. 67Gb. Free 54 Gb
DB is on driver D. 135 Gb. Free 80 Gb

There is already nothing running on the server. Or at least the same as the last 9 years (or 8 maybe. Can recall the exact date).
The server is restarted twice a week. Early monday and early friday.

According to my coworker this server is not behaving differently this week, as it did last week. Or the month before.
No errors in any logs. Except Firebird.

>
> As for the causes, I don't have a clue.
>
> Michael
>