环境配置及症状:
AS4U8+IDS9.21.UC2
$ONCONFIG
ALARMPROGRAM /home/informix/etc/log_full.sh # Alarm program path
bar_act.log
2011-10-14 13:48:40 8063 8061 /home/informix/bin/onbar_d -b -l
2011-10-14 13:48:40 8063 8061 Begin backup logical log 311991.
2011-10-14 13:48:40 8063 8061 Successfully connected to Storage Manager.
2011-10-14 13:48:40 8063 8061 ASSERT: file bar_xbsa.ecbarSendData() line 1331 - contact product support
2011-10-14 13:48:40 8063 8061 See also: /home/informix/tmp/core
online.log
13:48:39 Logical Log 311993 Complete.
13:48:40 Logical Log 311991 - Backup Started
13:48:40 Logical Log 311991 - Backup Aborted
Aborted by client.
13:48:40 Process exited with return code 139: /bin/sh /bin/sh -c /home/informix/etc/log_full.sh 2 23 "Logical Log 311993 Complete." "Logical Log 311993 Complete."
系统逻辑日志满时,自动触发/home/informix/etc/log_full.sh 进行逻辑日志备份,bar_act.log及online.log日志信息如上(手工进行逻辑日志备份正常)
原因:
与参数SHMVIRTSIZE (# initial virtual shared memory segment size)有关
解决办法:
将SHMVIRTSIZE值设置小一点,我的实例下,将原来参数调整为32000,如果调整后仍然有问题,试着重启一下ISM(ism_shutdown->ism_startup)
Use the SHMVIRTSIZE configuration parameter to specify the initial size of a virtual shared-memory segment.
64-bit platforms: Positive integer with a maximum value of 4 terabytes
The maximum value might be less on some platforms due to operating-system limitations. For the actual maximum value for your UNIX platform, see the machine notes.
To determine the appropriate value for the SHMVIRTSIZE configuration parameter, use the following algorithm to determine the size of the virtual portion of shared memory:
shmvirtsize = fixed overhead + ((stack size + heap) * number of users)
| Component | Value to use |
|---|---|
| Fixed overhead | This includes the size of the AIO vectors + sort memory + dbspace backup buffers + dictionary size + size of stored-procedure cache + histogram pool + other pools, and other overhead. To obtain an estimate of the fixed overhead, start the database server and see how many additional memory segments are allocated, if any. The number of users that you have on the system when you start the server, impacts the allocation of memory segments. When you start the server:
|
| Stack size | On 32-bit systems, use 32 kilobytes for the stack size. Typically on 64-bit systems, you use 64 kilobytes for the stack size. However, some 64-bit systems use a different value. For more information see the STACKSIZE configuration parameter. |
| Heap | Use 30 kilobytes per user. |
| Number of users | Use the maximum number of concurrent user sessions that you anticipate on the server. |
If possible, create a virtual portion of shared memory of a size that is more than you require for your daily processing.
Use the onstat -g seg command to determine peak usage and lower the value of the SHMVIRTSIZE configuration parameter accordingly.
The
SHMVIRTSIZEparameter in the Informix ONCONFIGfile specifies how much shared memory in KB to use for the "virtual portion" at system start. Informix stores various objects here, including the dictionary cache.
The most important factor affecting the size of virtual portion is the session pools. If a large number of users are very active, Informix adds memory to this area. This dynamic allocation of shared memory can affect performance considerably, so you should allocate a large initial segment to avoid dynamic increases. Use For up-to-date recommendations, see SAP Note 38307. Adjust the parameters
SHMVIRTSIZEand SHMADDto the actual storage requirements of the system for the following reasons:main screen of the database monitor to check for Virtual Portion in the Shared Memory display, which shows the value of SHMVIRTSIZE. Or you can execute the command onstat -g seg(as the user <sid>adm/informixor with transaction ST04), as in the following example:
Segment Summary: | |||||||
(resident segments are not locked) | |||||||
id | key | addr | size | ovhd | class | blkused | blkfree |
778 | 1381386243 | c0651000 | 679936 | 616 | M | 80 | 3 |
776 | 1381386241 | c072d000 | 46792704 | 1584 | R | 5708 | 4 |
777 | 1381386242 | c33cd000 | 8192000 | 732 | V | 1000 | 0 |
2331 | 1381386244 | d5fea000 | 8388608 | 732 | V | 1020 | 4 |
2844 | 1381386245 | d67ea000 | 8388608 | 732 | V | 536 | 488 |
Total | - | - | 72441856 | - | - | 8344 | 499 |
You can use the
Set the parameter
Take the sum of the size of the individual virtual shared memory segments (that is, the rows with the value This example of how to set SHMVIRTSIZE = 27,000 KB
本日志由 flyinweb 于 2011-10-14 14:11:17 发表,目前已经被浏览 579 次,评论 0 次;
作者添加了以下标签: Process exited with return code 139;
引用通告:http://www.517sou.net/Article/700/Trackback.ashx
而且直接配置文件是效率最高的,通过其它驱动效率都相对较低,BDB
这个测试不太准确,看官方的测试结果:http://bind-dlz.sourceforg
为什么使用BDB时QPS这么低? 我在bind版本基本相似的环境中测试的
It is quite useful and interesting too.
VIRT 的上限是64G,也就是36位, cat /proc/cpuinfo的结果是:addre
昨天要准备用线程重写webbench,试验了下Fedora Linux 2.6.35.14
不明白您的具体的意思是什么?
已经发送到你QQ邮箱