Limits in IBM Informix Dynamic Server

本文概述了 IBM Informix Dynamic Server 在 UNIX 操作系统上的容量限制、系统默认参数及访问能力。包括系统级参数、表级参数、最大数据库数量、活跃用户数等关键信息。

Appendix F.
The following sections list selected capacity limits and system defaults for IBM
Informix Dynamic Server.
Limitations on UNIX Operating Systems
System-Level Parameter Limits (UNIX)
System-Level Parameters Maximum Capacity per Computer System
IBM Informix Dynamic Server systems per
computer (Dependent on available system
resources)
255
Maximum number of accessible remote sites Machine specific
Maximum virtual shared memory segment
(SHMVIRTSIZE)
2GB (32-bit platforms) or 4TB (64-bit
platforms)
Maximum address space 1.7GB if boot.ini file not modified to 3GB
2.7GB if boot.ini file is modified to 3GB
Table-Level Parameter Limits (UNIX)
Table-Level Parameters (based on 2K page
size) Maximum Capacity per Table
Data rows per fragment 4,277,659,295
Data pages per fragment 16,775,134
Data bytes per fragment (excludes Smart
Large Objects (BLOB, CLOB) and Simple
Large Objects (BYTE, TEXT) created in
Blobspaces)
33,818,671,136
Binary Large Object BLOB/CLOB pages 4*2*40
Binary Large Objects TEXT/BYTE bytes 4*2*40
Row length 32,767
Number of columns 32K
Key parts per index 16
Columns per functional index 102 (for C UDRs) 341 (for SPL or Java
UDRs)
Maximum bytes per index key (for a given
page size):
2K page size = 387
4K page size = 796
8K page size = 1615
12K page size = 2435
16K page size = 3254
Maximum size of an SQL statement 64K


Access Capabilities (UNIX)
Access Capabilities
Maximum Capacity per
System
Maximum databases per Dynamic Server system 21 million
Maximum tables per Dynamic Server system 477,102,080
Maximum active users per Dynamic Server (minus the
minimum number of system threads)
32K user threads
Maximum active users per database and table (also limited
by the number of available locks, a tunable parameter)
32K user threads
Maximum number of open tables per Dynamic Server
system
Dynamic allocation
Maximum number of open tables per user and join Dynamic allocation
Maximum locks per Dynamic Server system and database Dynamic allocation
Maximum number of page cleaners 128
Maximum number of partitions per dbspace 4K page size: 1048445, 2K
page size: 1048314 (based on
4-bit bitmaps)
Maximum number of recursive synonym mappings 16
Maximum number of tables locked with LOCK TABLE per
user
32
Maximum number of cursors per user Machine specific
Maximum Enterprise Replication transaction size 4 TB
Maximum dbspace size 4 TB with 2K page size8 TB
with 4K page size
Maximum sbspace size 4 TB with 2K page size8 TB
with 4K page size
Maximum chunk size 4 TB
Maximum number of chunks 32,766
Maximum number of 2K pages per chunk 2 billion
Maximum number of open Simple Large Objects (applies
only to TEXT and BYTE data types)
20
Maximum number of B-tree levels 20
Maximum amount of decision support memory Machine specific
Maximum size of a Dynamic Server instance 8 PB
Utility support for large files 17 billion GB
Maximum number of storage spaces (dbspaces, blobspaces,
sbspaces, or extspaces)
2047
IBM Informix Dynamic Server System Defaults (UNIX)
Table lock mode Page
Initial extent size 8 pages
Next extent size 8 pages
Read-only isolation level (with database
transactions)
Committed Read
F-2 IBM Informix Dynamic Server Administrator’s Reference
Read-only isolation level (ANSI-compliant
database)

 

当NFSChina Server修改`limits.conf`不生效时,可以尝试以下解决办法: ### 1. 检查配置文件语法 确保`limits.conf`文件中的语法没有错误。错误的语法可能会导致配置无法正确加载。`limits.conf`文件的每一行通常遵循以下格式: ```plaintext <domain> <type> <item> <value> ``` 例如: ```plaintext * hard nofile 65536 * soft nofile 65536 ``` 可以使用文本编辑器仔细检查文件内容,确保没有拼写错误、多余的空格或其他语法问题。 ### 2. 检查配置文件是否被正确加载 `limits.conf`文件通常由`pam_limits.so`模块加载。需要确保`pam_limits.so`模块在相关的PAM(Pluggable Authentication Modules)配置文件中被正确引用。 一般来说,需要检查以下文件: - `/etc/pam.d/common-session` - `/etc/pam.d/common-session-noninteractive` 确保这些文件中包含以下行: ```plaintext session required pam_limits.so ``` ### 3. 重新登录会话 修改`limits.conf`后,新的配置通常需要在新的会话中生效。因此,需要重新登录用户会话,或者重启相关服务或系统。可以通过以下命令重新登录: ```bash exit # 然后重新登录 ``` ### 4. 检查系统服务 某些系统服务可能会有自己的资源限制设置,这些设置可能会覆盖`limits.conf`中的配置。需要检查NFS相关服务的配置文件,确保没有设置冲突的资源限制。 例如,对于NFS服务,可以检查`/etc/sysconfig/nfs`或`/etc/default/nfs-kernel-server`等文件。 ### 5. 检查SELinux或AppArmor SELinux(Security-Enhanced Linux)或AppArmor等安全机制可能会限制资源的使用,导致`limits.conf`的配置不生效。可以临时禁用SELinux或AppArmor来测试是否是这些安全机制的影响: - 对于SELinux,可以通过以下命令临时禁用: ```bash setenforce 0 ``` - 对于AppArmor,可以通过以下命令临时停止: ```bash sudo systemctl stop apparmor ``` 如果禁用后配置生效,需要调整SELinux或AppArmor的策略以允许所需的资源使用。 ### 6. 检查系统版本和内核限制 某些系统版本或内核可能有自己的资源限制,这些限制可能会覆盖`limits.conf`的配置。可以检查系统文档或内核参数,确保没有设置冲突的限制。 例如,可以通过以下命令查看当前的内核参数: ```bash sysctl -a | grep fs.file-max ``` 如果需要修改内核参数,可以编辑`/etc/sysctl.conf`文件,并添加或修改相关参数,然后执行以下命令使配置生效: ```bash sysctl -p ```
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值