博客
关于我
强烈建议你试试无所不能的chatGPT,快点击我
informix 10.0 extent size 的大小限制和数量限制
阅读量:2454 次
发布时间:2019-05-10

本文共 2027 字,大约阅读时间需要 6 分钟。

1,当我用create table创建一个extent size非常巨大的表时,得到:

19836:Extent Size is too large;

maxinum size of an extent id 33554430K

从上面可以看到大小的限制是:33554430K

2,我在导入大量数据的时候出现no more extents.查看错误代码:

:~> finderr 136

-136 ISAM error: no more extents.

The database server needs to add an extent to a table but cannot

do so. Either not enough disk space is available in the dbspace, or the
table has been given the maximum number of extents that is allowed. The
database server administrator can determine the cause as follows:

1. Determine the tblspace number for the table. It is the value in

the partnum column of the systables table for this table.

2. Convert the tblspace number to hexadecimal and extract its

most-significant 2 digits (the high-order byte). This chunk
number indicates where the table resides.

3. Use the tbstat or onstat utility -t option to find out disk

usage for this table. Note particularly the values reported for
npages (disk pages available), nused (disk pages used), and
nextns (number of extents).

If nused is less than npages, and nextns is large (over 200), the table

has too many extents. The upper limit of extents per table is between 200
and 50. The limit varies with the table definition and the
disk-page size in use. Reallocate the table using fewer, larger
extents. Unload the table data to a flat file. Drop the table.
Re-create the table, specifying a first-extent size sufficient to hold
all its current data and a next-extent size between one-fourth and
one-sixteenth its current size. Then reload the data into the table.

If nextns is small or the difference between npages and nused is less

than the size of the next-extent size for the table, not enough disk
space is available in the dbspace where the table resides. Use the
chunk number from step 2 and the ON-Monitor or ON-Monitor Chunks
display to determine the dbspace, then add a new chunk to that
dbspace.

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/312079/viewspace-245630/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/312079/viewspace-245630/

你可能感兴趣的文章
python cython_使用Cython为Python编写更快的C扩展
查看>>
flake8变量未使用_使用flake8确保Python代码的一致性
查看>>
ssh与gpg区别_如何使用GPG密钥启用SSH访问进行身份验证
查看>>
apm 韩国开源项目_韩国的开源状态
查看>>
mac上将视频变小_在Mac上将Python 3设置为默认的正确和错误方法
查看>>
java jnlp_Java SE 11删除JNLP的更好解决方案
查看>>
devops 中台_DevOps中的门控生产
查看>>
keil 开源替代_您需要替代开源的哪些专有工具?
查看>>
总论点和分论点_将破坏性的论点变成富有成效的对话
查看>>
pythonic_使用Pythonic在Python中以图形方式编程
查看>>
python black_格式化Python,但您喜欢使用Black
查看>>
如何在Mac上为Python设置虚拟环境
查看>>
使用Python在GitHub Pages上运行博客
查看>>
如何使用Python和Apache Spark分析日志数据
查看>>
移动端仿钉钉聊天 git_使用Git作为聊天的后端
查看>>
raspberry pi_PiFlash入门:在Linux上启动Raspberry Pi
查看>>
固态硬盘损坏数据如何挽救_开放数据和工具如何在灾难期间挽救生命
查看>>
raspberry_您最老的Raspberry Pi多大了?
查看>>
vscode构建rust_使用rust-vmm构建未来的虚拟化堆栈
查看>>
joplin_介绍Joplin,这是Evernote的开源替代方案
查看>>