informix插入資料包271,136錯誤
informix 匯入一個表,每次到到一個地方的時候就報,271,136錯誤:
> finderr 271
-271 Could not insert new row into the table.
This problem has many possible causes, including a locked table or a
full disk. Check the accompanying ISAM error code for more
information.
> 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.
>
但是檢視資料庫也明明有空間!表的擴充套件塊也都沒有用呢!
當時鍵表的時候用的擴充套件塊大小是最大的33554430K,(因為當時估計這個表的容量將特別大)
大家最後找到了原因:
是informix的限制,這個表的資料應該是當時達到了容量的限制。具體資訊在下面ibm的連結上。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/312079/viewspace-245632/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 【永春】往Sqlserver插入資料包錯SQLServer
- MySQL插入資料1366錯誤解決方案MySql
- Bmob插入資料顯示Error400錯誤的原因剖析Error
- 升級informix資料庫到10.0出現KAIO錯誤的解決辦法ORM資料庫AI
- INTERVAL分割槽插入大量資料導致ORA-4031錯誤
- linux oracle 建立informix dblink 錯誤解決LinuxOracleORM
- informix停資料庫是報錯:Must be a DBSA to run this programORM資料庫
- INFORMIX資料庫函式ORM資料庫函式
- MySQL 5.7 datetime和timestamp欄位設定default 0 插入資料包錯MySql
- mybatis插入資料、批量插入資料MyBatis
- Oracle用資料泵匯入資料包12899的錯誤碼解決方法Oracle
- 資料泵匯出資料包錯處理
- 安裝informix for nt時報錯ORM
- Informix資料庫安裝 Q&AORM資料庫
- informix資料庫啟動失敗ORM資料庫
- Mycat+Mysql 插入資料包錯 i[Err] 1064 - partition table, insert must provide ColumnListMySqlIDE
- 假資料填充錯誤記錄
- 大資料,還是大錯誤?大資料
- python中sklearn包的錯誤Python
- mongodb 插入資料MongoDB
- 插入單引號在oracle和informix中的區別OracleORM
- informix資料庫擴容操作步驟ORM資料庫
- Informix資料庫備份與恢復ORM資料庫
- informix資料空間映象操作步驟ORM
- informix資料庫onstat命令解釋大全ORM資料庫
- 用觸發器返回錯誤提示,糾正錯誤資料錄入觸發器
- SQL Server DACPAC資料庫部署錯誤SQLServer資料庫
- 資料庫ORA-0060錯誤資料庫
- 硬核圖解TCP粘包 資料包:我只是犯了每個資料包都會犯的錯圖解TCP
- 用SQL Server資料庫處理資料層錯誤SQLServer資料庫
- [譯] Go 1.13 errors 包錯誤處理GoError
- 六、函式、包和錯誤處理函式
- Maven建立專案遇到導包錯誤:Maven
- 求救:weblogic9+sql2000+CMP實現資料插入時的java.lang.AbstractMethodError錯誤WebSQLJavaError
- ORA-01653錯誤是Oracle資料庫中常見的錯誤Oracle資料庫
- mongodb資料庫中插入資料MongoDB資料庫
- 將informix匯出的文字資料匯入oracle資料庫ORMOracle資料庫
- oracle批量插入資料Oracle