Malc wrote:
This happens very occasionally (annually at worst) while the engine's
up and running, some users complain that access is slow for a minute
or so but there seem to be no detrimental effects - any clues?
What does the "Initialization failure" refer to?

IDS9.30HC5 on HP-UX 11i

09:29:33  WARNING! Physical Log size 15000 is too
small.
          Physical Log overflows may occur during peak
activity.
          Recommended minimum Physical Log size is 20 times
maximum
          concurrent user threads.

It means "Blimey gov, 9.30!!" :)

It means that you are getting to 75% Physical Log full, and a checkpoint may not get through quick enough to clear it down.

If you really want to get rid of the message just increase the physical log from your current 30 Mb to, say 60 Mb.

Malc wrote:
On 2 Oct, 10:01, theBP <th... at (no spam) Usenet-News.Net> wrote:
Malc wrote:
This happens very occasionally (annually at worst) while the engine's
up and running, some users complain that access is slow for a minute
or so but there seem to be no detrimental effects - any clues?
What does the "Initialization failure" refer to?
IDS9.30HC5 on HP-UX 11i
09:29:33  WARNING! Physical Log size 15000 is too
small.
          Physical Log overflows may occur during peak
activity.
          Recommended minimum Physical Log size is 20 times
maximum
          concurrent user threads.
It means "Blimey gov, 9.30!!" :)

It means that you are getting to 75% Physical Log full, and a checkpoint may not get through quick enough to clear it down.

If you really want to get rid of the message just increase the physical log from your current 30 Mb to, say 60 Mb.

Look, we've been on 9.30(HC5) since it came out, and it was hard
enough getting clearance to have that installed over 7.31UC2!
We just found a process respawning itself like mad, we were up to 537
connections (normal number is 160 or so)  so killing that off has
sorted it out.

Still wondering why we got the "Initialization failure" message - was
it trying to start a VP of some sort? (probably a PIO?)

Where do you see that message?

This happens very occasionally (annually at worst) while the engine's
up and running, some users complain that access is slow for a minute
or so but there seem to be no detrimental effects - any clues?
What does the "Initialization failure" refer to?

IDS9.30HC5 on HP-UX 11i

09:29:33 WARNING! Physical Log size 15000 is too
small.
Physical Log overflows may occur during peak
activity.
Recommended minimum Physical Log size is 20 times
maximum
concurrent user threads.

On 2 Oct, 10:01, theBP <th... at (no spam) Usenet-News.Net> wrote:
Malc wrote:
This happens very occasionally (annually at worst) while the engine's
up and running, some users complain that access is slow for a minute
or so but there seem to be no detrimental effects - any clues?
What does the "Initialization failure" refer to?
IDS9.30HC5 on HP-UX 11i
09:29:33 WARNING! Physical Log size 15000 is too
small.
Physical Log overflows may occur during peak
activity.
Recommended minimum Physical Log size is 20 times
maximum
concurrent user threads.
It means "Blimey gov, 9.30!!" :)

It means that you are getting to 75% Physical Log full, and a checkpoint may not get through quick enough to clear it down.

If you really want to get rid of the message just increase the physical log from your current 30 Mb to, say 60 Mb.

Look, we've been on 9.30(HC5) since it came out, and it was hard
enough getting clearance to have that installed over 7.31UC2!
We just found a process respawning itself like mad, we were up to 537
connections (normal number is 160 or so) so killing that off has
sorted it out.

Still wondering why we got the "Initialization failure" message - was
it trying to start a VP of some sort? (probably a PIO?)

Initialization failure probably means that someone or some task tried to
start the engine while it was already running.  Look for some logic that
says something like: "This is taking too long, IDS must be down, start it
up!"

Art

On 2 Oct, 10:28, theBP <th... at (no spam) Usenet-News.Net> wrote:
Malc wrote:
On 2 Oct, 10:01, theBP <th... at (no spam) Usenet-News.Net> wrote:
Malc wrote:
This happens very occasionally (annually at worst) while the engine's
up and running, some users complain that access is slow for a minute
or so but there seem to be no detrimental effects - any clues?
What does the "Initialization failure" refer to?
IDS9.30HC5 on HP-UX 11i
09:29:33 WARNING! Physical Log size 15000 is too
small.
Physical Log overflows may occur during peak
activity.
Recommended minimum Physical Log size is 20 times
maximum
concurrent user threads.
It means "Blimey gov, 9.30!!" :)

It means that you are getting to 75% Physical Log full, and a
checkpoint may not get through quick enough to clear it down.

If you really want to get rid of the message just increase the
physical log from your current 30 Mb to, say 60 Mb.

Look, we've been on 9.30(HC5) since it came out, and it was hard
enough getting clearance to have that installed over 7.31UC2!
We just found a process respawning itself like mad, we were up to 537
connections (normal number is 160 or so) so killing that off has
sorted it out.

Still wondering why we got the "Initialization failure" message - was
it trying to start a VP of some sort? (probably a PIO?)

Where do you see that message?

Comes up in the message log and in the call to ALARMPROGRAM it is sent
as an Alert 7, severity 3
_______________________________________________
Informix-list mailing list
Informix-list at (no spam) iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

On 2 Oct, 14:25, Art Kagel <art.ka... at (no spam) gmail.com> wrote:

Initialization failure probably means that someone or some task tried to
start the engine while it was already running.  Look for some logic that
says something like: "This is taking too long, IDS must be down, start it
up!"

Art

Not a chance. There's nothing automated about startup, it's entirely
dba-controlled; there's not a script anywhere that contains oninit and
dba/informix logins are tightly locked down.

On 2 Oct, 14:38, Malc <i... at (no spam) perrior.net> wrote:

On 2 Oct, 14:25, Art Kagel <art.ka... at (no spam) gmail.com> wrote:


Initialization failure probably means that someone or some task tried to
start the engine while it was already running. Look for some logic that
says something like: "This is taking too long, IDS must be down, start it
up!"

Art

Not a chance. There's nothing automated about startup, it's entirely
dba-controlled; there's not a script anywhere that contains oninit and
dba/informix logins are tightly locked down.


What is the full message from the online log?

_______________________________________________
Informix-list mailing list
Informix-list at (no spam) iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

da... at (no spam) smooth1.co.uk wrote:
On 2 Oct, 14:38, Malc <i... at (no spam) perrior.net> wrote:

On 2 Oct, 14:25, Art Kagel <art.ka... at (no spam) gmail.com> wrote:

Initialization failure probably means that someone or some task tried to
start the engine while it was already running.  Look for some logic that
says something like: "This is taking too long, IDS must be down, start it
up!"

Art

Not a chance. There's nothing automated about startup, it's entirely
dba-controlled; there's not a script anywhere that contains oninit and
dba/informix logins are tightly locked down.

What is the full message from the online log?

That WAS the full message:

09:29:33  WARNING! Physical Log size 15000 is too small.
         Physical Log overflows may occur during peak activity.
         Recommended minimum Physical Log size is 20 times maximum
         concurrent user threads.

There'd been a checkpoint a couple of minutes before.
The Alert 7 (Severity 3) call to ALARMPROGRAM contained the same message.

We did find a looping 4gl process that had respawned itself several
hundred times which we killed. We'd got to 570 connections to the engine
(shm connections) when we usually run at 160 - 200 or so; we've got
NETTYPE for shm set to 2 200 (as I recall; I'm not logged in to work at
present).

_______________________________________________
Informix-list mailing list
Informix-l... at (no spam) iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

On 3 Oct, 19:27, malc_p <i... at (no spam) perrior.net> wrote:



da... at (no spam) smooth1.co.uk wrote:
On 2 Oct, 14:38, Malc <i... at (no spam) perrior.net> wrote:

On 2 Oct, 14:25, Art Kagel <art.ka... at (no spam) gmail.com> wrote:

Initialization failure probably means that someone or some task tried to
start the engine while it was already running.  Look for some logic that
says something like: "This is taking too long, IDS must be down, start it
up!"

Art

Not a chance. There's nothing automated about startup, it's entirely
dba-controlled; there's not a script anywhere that contains oninit and
dba/informix logins are tightly locked down.

What is the full message from the online log?

That WAS the full message:

09:29:33  WARNING! Physical Log size 15000 is too small.
         Physical Log overflows may occur during peak activity.
         Recommended minimum Physical Log size is 20 times maximum
         concurrent user threads.

There'd been a checkpoint a couple of minutes before.
The Alert 7 (Severity 3) call to ALARMPROGRAM contained the same message.

We did find a looping 4gl process that had respawned itself several
hundred times which we killed. We'd got to 570 connections to the engine
(shm connections) when we usually run at 160 - 200 or so; we've got
NETTYPE for shm set to 2 200 (as I recall; I'm not logged in to work at
present).

_______________________________________________
Informix-list mailing list
Informix-l... at (no spam) iiug.org
http://www.iiug.org/mailman/listinfo/informix-list

Tell a lie, NETTYPE for ipcshm is 2,230 so going over 460 connections
would have caused the engine some consternation, but surely it should
have just refused further attempts?

Still can't see why the Initialization Failure alert was sent out.