Re: IDS GE license restriction limits warning messages...
Posted in 2010
Good catch Art, fixed that but as you have stated it had nothing to do with it.
----- Original Message -----
From: "Art Kagel" <art.kagel@gmail.com>
To: "June Nebab" <jnebab@idealcut.com>
Cc: "jrenaut" <jprenaut@yahoo.com>, informix-list@iiug.org
Sent: Thursday, December 16, 2010 1:59:58 PM GMT -05:00 US/Canada Eastern
Subject: Re: IDS GE license restriction limits warning messages...
June:
This one setting, at least, is not correct:
SHMNOACCESS cpu,num=1,noage
This looks like your SHMNOACCESS and VPCLASS settings got combined somehow. Don't think this has anything to do with the warning you are seeing, but....
Art
Art S. Kagel
Advanced DataTools ( www.advancedatatools.com )
IIUG Board of Directors ( art@iiug.org )
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.
On Thu, Dec 16, 2010 at 1:28 PM, June Nebab < jnebab@idealcut.com > wrote:
Jacques,
After mistakenly admitting that this worked, I noticed the same error messages still appearing in the log whenever I startup the engine.
IFX_LARGE_PAGES environment is already set to 1.
cat /proc/meminfo shows the following HugePages settings:
HugePages_Total: 0
HugePages_Free: 0
HugePages_Rsvd: 0
Hugepagesize: 2048 kB
I changed RESIDENT from "-1" to "1" and bounced the engine but the message still appears.
My shared memory settings in ONCONFIG:
RESIDENT 1
SHMBASE 0x44000000
SHMVIRTSIZE 1024000
SHMADD 8192
EXTSHMADD 8192
SHMTOTAL 0
SHMVIRT_ALLOCSEG 0.000000,3
SHMNOACCESS cpu,num=1,noage
On Thu, Dec 2, 2010 at 10:28 AM, jrenaut < jprenaut@yahoo.com > wrote:
On Nov 30, 4:08 pm, June Nebab LKINY < jne...@idealcut.com > wrote:
> On a new install of IDS 11.70 UC1GE on Red Hat Enterprise 5 32 bit with 6GB RAM. I noticed the following messages in the online.log file:
>
> 14:07:32 Warning: The IBM IDS Growth Edition license restriction limits
> 14:07:32 the total shared memory size for this server to 0 KB.
> 14:07:32 The maximum allowable shared memory was reset to this size to start the database server.
> 14:07:32 Insufficient free huge pages in /proc/meminfo for shared memory segment.
> Requested: 142397440 bytes. Available: 0 bytes.
> The default memory page size will be used.
> 14:07:32 Segment locked: addr=0x44000000, size=142397440
> 14:07:32 Insufficient free huge pages in /proc/meminfo for shared memory segment.
> Requested: 655360000 bytes. Available: 0 bytes.
> The default memory page size will be used.
> 14:07:32 Segment locked: addr=0x4c7cd000, size=655360000
>
> My SHMVIRTSIZE is set to 640000 KB
>
> DISCLAIMER
>
> This transmission and the information contained herein and/or in any attachments hereto and/or in any attachments thereto is privileged and/or confidential and is intended ONLY for the use of the individual(s) and/or entity(s) named above. If you are not the intended recipient, you are strictly prohibited from disclosing, printing, copying, using or disseminating this transmission and/or any such attachments and any information contained in this transmission and/or in any such attachments. ANY unauthorized interception of this transmission and/or any such attachments is a violation of federal criminal law.
>
> If you have received this transmission in error, please notify the sender immediately and delete the transmission and all such attachments
To get those messages it appears you need to have the env variable
IFX_LARGE_PAGES set to 1. If that is turned on, then when trying to
start up the server and create the initial shared memory segments, the
oninit process will open up /proc/meminfo looking for HugePages_Free
and Hugepagesize. I'm not familiar with this concept on Linux, but I
would assume it is some sort of OS configuration thing. From the
message you got, it would appear that we found Hugepagesize set to be
0 from our query to /proc/meminfo, at which point we would no longer
attempt to use that feature.
Jacques Renaut
IBM Informix Advanced Support
APD Team
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
DISCLAIMER
This transmission and the information contained herein and/or in any attachments hereto and/or in any attachments thereto is privileged and/or confidential and is intended ONLY for the use of the individual(s) and/or entity(s) named above. If you are not the intended recipient, you are strictly prohibited from disclosing, printing, copying, using or disseminating this transmission and/or any such attachments and any information contained in this transmission and/or in any such attachments. ANY unauthorized interception of this transmission and/or any such attachments is a violation of federal criminal law.
If you have received this transmission in error, please notify the sender immediately and delete the transmission and all such attachments