 | |
IDS GE license restriction limits warning messages...
comp.databases.informix comp.databases.informix
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
IDS GE license restriction limits warning messages... -
11-30-2010
, 04:08 PM
#2
| |||
| |||
|
|
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.. _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
--
Alexandre Marini
Tecnologia da Informação - DBA
SEFAZ-MS / SGI-UGSR / Sistemas IBM-Informix
Cert-Info-Mgmt_color <Cert-Info-Mgmt_color.jpg>
IBM Informix Dynamic Server Certified Professional V10 / V11
#3
| |||
| |||
|
|
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 senderimmediately and delete the transmission and all such attachments |
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
#4
| |||
| |||
|
|
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 |
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 (AT) iiug (DOT) 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
#5
| |||
| |||
|
|
On Nov 30, 4:08 pm, June Nebab LKINY <jne... (AT) idealcut (DOT) 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 (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#6
| |||
| |||
|
|
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 (AT) yahoo (DOT) com> wrote: On Nov 30, 4:08 pm, June Nebab LKINY <jne... (AT) idealcut (DOT) 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 (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#7
| |||
| |||
|
|
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 |
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 (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) 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
#8
| |||
| |||
|
|
Good catch Art, fixed that but as you have stated it had nothing to do with it. ----- Original Message ----- From: "Art Kagel" <art.kagel (AT) gmail (DOT) com To: "June Nebab" <jnebab (AT) idealcut (DOT) com Cc: "jrenaut" <jprenaut (AT) yahoo (DOT) com>, informix-list (AT) iiug (DOT) 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 (AT) iiug (DOT) 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 (AT) idealcut (DOT) 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 (AT) yahoo (DOT) com> wrote: On Nov 30, 4:08 pm, June Nebab LKINY <jne... (AT) idealcut (DOT) 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 (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) 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. _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
#9
| |||
| |||
|
|
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 |
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 (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) 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.
_______________________________________________
Informix-list mailing list
Informix-list (AT) iiug (DOT) org
http://www.iiug.org/mailman/listinfo/informix-list
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
_______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) 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
#10
| |||
| |||
|
|
Output of onstat -g env IBM Informix Dynamic Server Version 11.70.UC1GE -- On-Line -- Up 21:42:09 -- 1164112 Kbytes Server start-up environment: Variable Value [values-list] DBDELIMITER | DBPATH . DBPRINT lp -s DBTEMP /tmp IFX_LARGE_PAGES 1 INFORMIXDIR /u/informix/11_7 [/u/informix/11_7] [/usr/informix] INFORMIXSERVER prod117_net INFORMIXSQLHOSTS /u/informix/11_7/etc/sqlhosts INFORMIXTERM termcap [termcap] [terminfo] LANG en_US.UTF-8 LC_COLLATE en_US.UTF-8 LC_CTYPE en_US.UTF-8 LC_MONETARY en_US.UTF-8 LC_NUMERIC en_US.UTF-8 LC_TIME en_US.UTF-8 LKNOTIFY yes LOCKDOWN no NODEFDAC no ONCONFIG onconfig.prod117 PATH /u/bin:/u/informix/11_7:/u/informix/11_7/bin:/u1/tmp:/u/informix/11_7/lib:/u/informix/11_7/lib/esql:/usr/kerberos/bin:/usr/bin:/bin:/opt/mx/bin SERVER_LOCALE en_US.819 SHELL /bin/bash TERM wyse60 [wyse60] [dumb] TERMCAP /u/informix/11_7/etc/termcap [/u/informix/11_7/etc/termcap] [/etc/termcap] Output of /etc/systcl.conf: # Kernel sysctl configuration file for Red Hat Linux # # For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and # sysctl.conf(5) for more details. # Controls IP packet forwarding net.ipv4.ip_forward = 0 # Controls source route verification net.ipv4.conf.default.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 # Controls the System Request debugging functionality of the kernel kernel.sysrq = 0 # Controls whether core dumps will append the PID to the core filename # Useful for debugging multi-threaded applications kernel.core_uses_pid = 1 # Controls the use of TCP syncookies net.ipv4.tcp_syncookies = 1 # Controls the maximum size of a message, in bytes kernel.msgmnb = 65536 # Controls the default maxmimum size of a mesage queue kernel.msgmax = 65536 # Controls the maximum number of shared memory segments, in pages # Default RHEL 5 kernel.shmmax value # JN11/16/2010 - commented this line in favor of the IDS 11.7 params below # kernel.shmall = 268435456 # Controls the maximum shared segment size, in bytes # Default RHEL 5 kernel.shmmax value # JN11/16/2010 - commented this line in favor of the IDS 11.7 params below # kernel.shmmax = 4294967295 # JN11/16/2010 - LKI RHEL5 IDS11.7 customization kernel.shmmax = 33554432 kernel.shmmni = 128 kernel.shmall = 4194304 kernel.semmni = 128 kernel.semmsl = 250 kernel.semmns = 32000 kernel.semopm = 32 Output of /proc/meminfo MemTotal: 6221460 kB MemFree: 59016 kB Buffers: 322876 kB Cached: 5391484 kB SwapCached: 0 kB Active: 901384 kB Inactive: 5002172 kB HighTotal: 5363900 kB HighFree: 48312 kB LowTotal: 857560 kB LowFree: 10704 kB SwapTotal: 6144744 kB SwapFree: 6144424 kB Dirty: 1108 kB Writeback: 0 kB AnonPages: 189180 kB Mapped: 388060 kB Slab: 219416 kB PageTables: 9484 kB NFS_Unstable: 0 kB Bounce: 0 kB CommitLimit: 9255472 kB Committed_AS: 1997636 kB VmallocTotal: 116728 kB VmallocUsed: 20352 kB VmallocChunk: 96128 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 Hugepagesize: 2048 kB ------------------------------------- June A. Nebab IBM Informix DBA/Linux System Admin Lazare Kaplan International Inc. 19 W 44th Street New York, NY 10036 800-554-3325 212-972-9700 "The World's Most Beautiful Diamond" www.lazarediamonds.com ----- Original Message ----- From: "Fernando Nunes" <domusonline (AT) gmail (DOT) com To: informix-list (AT) iiug (DOT) org Sent: Thursday, December 16, 2010 7:06:49 PM GMT -05:00 US/Canada Eastern Subject: Re: IDS GE license restriction limits warning messages... Can you post the output of "onstat -g env"? Regards. On Thu, Dec 16, 2010 at 8:58 PM, June Nebab LKINY <jnebab (AT) idealcut (DOT) com>wrote: Good catch Art, fixed that but as you have stated it had nothing to do with it. ----- Original Message ----- From: "Art Kagel" <art.kagel (AT) gmail (DOT) com To: "June Nebab" <jnebab (AT) idealcut (DOT) com Cc: "jrenaut" <jprenaut (AT) yahoo (DOT) com>, informix-list (AT) iiug (DOT) 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 (AT) iiug (DOT) 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 (AT) idealcut (DOT) 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 (AT) yahoo (DOT) com> wrote: On Nov 30, 4:08 pm, June Nebab LKINY <jne... (AT) idealcut (DOT) 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 (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) 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. _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) 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. |
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.