Limits in HCL OneDB
This topic lists the system-level and table-level parameter limits, the system defaults, and the access capabilities of HCL OneDB™.
- System-Level Parameter Limits
- Table-level parameter limits
- HCL OneDB System Defaults
- Access capabilities
System-Level Parameter Limits
System-Level Parameters | Maximum Capacity per Computer System |
---|---|
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 number of HCL OneDB shared memory segments | 1024 |
Maximum address space | UNIX: Machine
specific Windows: 2.7 GB if 4-gigabyte tuning is enabled:
1.7 GB for Windows 2003 and earlier versions if the
boot.ini file does not contain the |
Table-level parameter limits
Table-level parameters (2K page size unless otherwise stated) | Maximum capacity per table |
---|---|
Data rows per page | 255 |
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 |
2K page size = 33,818,670,144 |
Binary large object BLOB/CLOB pages | 4 TB |
Binary large objects TEXT/BYTE bytes | 4 TB |
Row length | 32,767 |
Number of columns | 32K |
Maximum number of pages per index fragment | 2,147,483,647 |
Key parts per index | 16 |
Columns per functional index | 102 (for C UDRs) 341 (for SPL or Java™ UDRs) |
Maximum bytes per index key: |
2K page size = 387 |
Maximum size of an SQL statement | Limited only by available memory |
HCL OneDB System Defaults
Database characteristic | HCL OneDB system default |
---|---|
Table lock mode | Page |
Initial extent size | 8 pages |
Next extent size | 8 pages |
Read-only isolation level (with database transactions) | Committed Read |
Read-only isolation level (ANSI-compliant database) | Repeatable Read |
Access capabilities
Access Capabilities | Maximum Capacity per System |
---|---|
Maximum databases per HCL OneDB system | 21 million |
Maximum tables per HCL OneDB system | 477 102 080 |
Maximum active users per HCL OneDB (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 databases in a session | UNIX: 32 databases Windows: 8 databases |
Maximum number of open tables per HCL OneDB system | Dynamic allocation |
Maximum number of open tables per user and join | Dynamic allocation |
Maximum number of open transactions per instance | 32 767 |
Maximum locks per HCL OneDB 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 | 131 PB |
Maximum sbspace size | 131 PB |
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 |
Utility support for large files | 17 billion GB |
Maximum number of storage spaces (dbspaces, blobspaces, sbspaces, or extspaces) | 2047 |