IDS GE license restriction limits warning messages...

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

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