Allocating memory segments without apparent reason
Posted in 2004
Topics: Logging & Checkpoints, Versions, Editions & End-of-Life
Scenario: IDS 7.3 UC5 AIX 4.3.3 - LEVEL 11 Our system have been working fine for a long time. Last Tuesday, without = =3D any change on the configuration the system stopped. In less than 1 = =3D minute and without an excesive load in the system, Informix = allocated =3D all memory segments as it could. It was still On Line, but = no more =3D connections were allowed. It seems than the problem could be = related =3D with a backup operation (logical log, ...) Any help would be apreciated. Thank you.=20 ------------------------------------------------------------------------ Log. 03:54:55 Checkpoint Completed: duration was 1 seconds. 03:59:33 = Logical Log 3104 Complete. 03:59:36 Logical Log 3104 - Backup Started = 03:59:36 Logical Log 3104 - Backup Aborted Aborted by client. 03:59:43 Process exited with return code 133: /bin/sh /bin/sh -c =3D = /usr/informix/ etc/log_full.sh 2 23 "Logical Log 3104 Complete." = "Logical Log 3104 =3D Complete."=20 03:59:57 Checkpoint Completed: duration was 2 seconds.=20 04:04:59 Checkpoint Completed: duration was 2 seconds.=20 04:08:21 dynamically allocated new shared memory segment (size = =3D67108864) 04:08:33 dynamically allocated new shared memory segment (size = =3D67108864) 04:08:48 dynamically allocated new shared memory segment (size = =3D67108864) 04:09:01 dynamically allocated new shared memory segment (size = =3D67108864) 04:09:16 dynamically allocated new shared memory segment (size = =3D67108864) 04:09:32 dynamically allocated new shared memory segment (size = =3D67108864) ________________________________________ Domingo Fern=E1ndez Servicio de Inform=E1tica Universidad de Cantabria Tfno: 942201084 Fax: 942201083 e-mail: Domingo.Fernandez@gestion.unican.es
Hi,
I don't think that the allocation of memeory has to do with the (aborted)
logical log backup. Since you get the message that the log backup was
"borted by the client", the server most probably properly closed down
the session and threads associated with that aborted log backup.
There's activity on your system, otherwise your checkpoints (done
every 5 minutes, 300 seconds intervall from your $ONCONFIG I guess),
wouldn't take 2 seconds. Without any activity you would not have
a checkpoint at all, and with little activity it would show duration of
zero seconds (rather than 2 seconds).
In hindsight it is difficult to tell which activity on the system caused
the allocation of more memory (and perhaps depleted some other
resources for connecting sessions). If the situation persists, you can
try to gather some info with commands like "onstat -g ses",
"onstat -g mem" to find out where the additional memory is used,
"onstat -g ses <session number>" to find out, what a specific session
is doing, etc.
If the situation does not persist, you may try "onmode -F" to free unused
memory (though this will work only if whole segments are unused).
Regards,
Martin
--
Martin Fuerderer
IBM Informix Development Munich
Data Management Solutions
forum.subscriber@iiug.org wrote on 09.07.2004 13:34:02:
> Scenario:
> IDS 7.3 UC5
> AIX 4.3.3 - LEVEL 11
>
> Our system have been working fine for a long time. Last Tuesday, without
=
> =3D any change on the configuration the system stopped. In less than 1 =
> =3D minute and without an excesive load in the system, Informix =
> allocated =3D all memory segments as it could. It was still On Line, but
=
> no more =3D connections were allowed. It seems than the problem could be
=
> related =3D with a backup operation (logical log, ...)
>
> Any help would be apreciated.
>
> Thank you.=20
> ------------------------------------------------------------------------
>
> Log.
> 03:54:55 Checkpoint Completed: duration was 1 seconds. 03:59:33 =
> Logical Log 3104 Complete. 03:59:36 Logical Log 3104 - Backup Started =
> 03:59:36 Logical Log 3104 - Backup Aborted
> Aborted by client.
> 03:59:43 Process exited with return code 133: /bin/sh /bin/sh -c =3D =
> /usr/informix/ etc/log_full.sh 2 23 "Logical Log 3104 Complete." =
> "Logical Log 3104 =3D Complete."=20
> 03:59:57 Checkpoint Completed: duration was 2 seconds.=20
> 04:04:59 Checkpoint Completed: duration was 2 seconds.=20
> 04:08:21 dynamically allocated new shared memory segment (size =
> =3D67108864)
> 04:08:33 dynamically allocated new shared memory segment (size =
> =3D67108864)
> 04:08:48 dynamically allocated new shared memory segment (size =
> =3D67108864)
> 04:09:01 dynamically allocated new shared memory segment (size =
> =3D67108864)
> 04:09:16 dynamically allocated new shared memory segment (size =
> =3D67108864)
> 04:09:32 dynamically allocated new shared memory segment (size =
> =3D67108864)
>
>
>
> ________________________________________
> Domingo Fern=E1ndez
> Servicio de Inform=E1tica
> Universidad de Cantabria
> Tfno: 942201084
> Fax: 942201083
> e-mail: Domingo.Fernandez@gestion.unican.es
>
>
>
Would you know what the logical log backup was doing when it aborted? Was it continuous backup or did it abort on the first log of a manual backup? If it was a manual backup, were all other logs full too? Best regards, Andy. >From: "Fernandez G...." <domingo.fernandez@gestion.unican.es> >To: ids@iiug.org >Subject: Allocating memory segments without apparent reason [3216] Date: >Fri, 9 Jul 2004 07:34:02 -0400 (EDT) > >Scenario: >IDS 7.3 UC5 >AIX 4.3.3 - LEVEL 11 > >Our system have been working fine for a long time. Last Tuesday, without = >=3D any change on the configuration the system stopped. In less than 1 = >=3D minute and without an excesive load in the system, Informix = >allocated =3D all memory segments as it could. It was still On Line, but = >no more =3D connections were allowed. It seems than the problem could be = >related =3D with a backup operation (logical log, ...) > >Any help would be apreciated. > >Thank you.=20 >------------------------------------------------------------------------ > >Log. >03:54:55 Checkpoint Completed: duration was 1 seconds. 03:59:33 = >Logical Log 3104 Complete. 03:59:36 Logical Log 3104 - Backup Started = >03:59:36 Logical Log 3104 - Backup Aborted > Aborted by client. >03:59:43 Process exited with return code 133: /bin/sh /bin/sh -c =3D = >/usr/informix/ etc/log_full.sh 2 23 "Logical Log 3104 Complete." = >"Logical Log 3104 =3D Complete."=20 >03:59:57 Checkpoint Completed: duration was 2 seconds.=20 >04:04:59 Checkpoint Completed: duration was 2 seconds.=20 >04:08:21 dynamically allocated new shared memory segment (size = >=3D67108864) >04:08:33 dynamically allocated new shared memory segment (size = >=3D67108864) >04:08:48 dynamically allocated new shared memory segment (size = >=3D67108864) >04:09:01 dynamically allocated new shared memory segment (size = >=3D67108864) >04:09:16 dynamically allocated new shared memory segment (size = >=3D67108864) >04:09:32 dynamically allocated new shared memory segment (size = >=3D67108864) > > > >________________________________________ >Domingo Fern=E1ndez >Servicio de Inform=E1tica >Universidad de Cantabria >Tfno: 942201084 >Fax: 942201083 >e-mail: Domingo.Fernandez@gestion.unican.es > > > _________________________________________________________________ It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
Related threads
- Posting from the Informix-list
- Migrating from IDS 9.40.UC6 to 11.50.UC3
- Ip for a network session
- questions onstat -g