Hi Mike,

Not in this case. The original install on this platform was an unpatched II10.0.0 (a64.lnx/132). I just added the patch to it.

The problem has not reoccurred since. I think I'll wait and see if its justa one off case of gremlins.

Marty

From: Michael Dyer [mailto:Michael.Dyer (AT) ingres (DOT) com]
Sent: 23 March 2011 07:10
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] When does a bad size expand lead to E_DM00A0?

Anyone seen this before?
Yes. We currently have a client issue where the behaviour was reported.
The behaviour could not be replicated when applying this patch to a freshlyinstalled II 10.0.0 (a64.lnx/132).
(Neither at the client site, nor in-house.)

Then we noticed that config.dat revealed that the installation started out as II 10.0.0 (a64.lnx/125). (A GPL version)


If you have been testing using the GPL version, do not attempt to upgrade the installation to the Enterprise Supported version.
Unload your databases and reload in a freshly installed II 10.0.0 (a64.lnx/132).

Cheers,
Michael

________________________________
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Martin Bowes
Sent: 22 March 2011 11:19
To: Ingres and related product discussion forum
Subject: [Info-Ingres] When does a bad size expand lead to E_DM00A0?

Hi All,

Having recently installed p14025 to a server running II 10.0.0 (a64.lnx/132)NPTL.

DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, sc0m.c:1384 ]: Mon Mar 21 19:00:17 2011 E_SC0107_BAD_SIZE_EXPAND Error expanding virtual size of server.
mepages.c:1151 brk() failed with operating system error 12 (Cannot allocate memory)
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, scumsvc.c:295 ]: Mon Mar 21 19:00:17 2011 E_SC0107_BAD_SIZE_EXPAND Error expanding virtual size of server.
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, scumsvc.c:295 ]: Mon Mar 21 19:00:17 2011 E_SC0107_BAD_SIZE_EXPAND Error expanding virtual size of server.
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, dm0m.c:761 ]: Mon Mar 21 19:00:17 2011 E_DM9425_MEMORY_ALLOCATE Error allocating memory for DMF operation. Could not allocate requested memory. Memory request was for 4194304 bytes.
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, dm0m.c:762 ]: Mon Mar 21 19:00:17 2011 E_DM9429_EXPAND_POOL Error in expand_pool() adding to the virtual address space of the process.
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, scsdbfcn.c:865 ]: Mon Mar 21 19:00:17 2011 E_SC0121_DB_OPEN Error opening database. Name: reveal_internal_dev Owner: reveal Access Mode: 00000002 Flags 40000000
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, scsdbfcn.c:874 ]: Mon Mar 21 19:00:17 2011 E_SC010D_DB_LOCATION Database Location Name: $default Physical Specification: /dbdata1/II/ingres/data/default/reveal_internal_dev Flags: 00000003
DECIUS_CTSU_OX_AC_::[51605 , 22965 , 000000003ae36200, scsinit.c:4338 ]: Mon Mar 21 19:00:17 2011 E_DM00A0_UNKNOWN_COLLATION Could not open a database because collation sequence not installed.

The database in question was not created with a specific collation sequence.. So I assume something about the Bad size expand managed to trigger the E_DM00A0 message.

I've checked the DBMS log and there is nothing in there that would shed anylight on this problem.

Anyone seen this before?

Martin Bowes

Thanks Paul,

That's a big help.

Marty

-----Original Message-----
From: Paul Mason [mailto:Paul.Mason (AT) ingres (DOT) com]
Sent: 23 March 2011 09:21
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] When does a bad size expand lead to E_DM00A0?

If you want DM420 via IMA have a look at KB doc 416740 - it might save
you a little time.



_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres