bad isam file format
Burkhard Obergoker got a bad isam file format error running dbimport of a roughly 2 GB database for a 4GL application on IDS 7.30 under Linux 2.2.12; the schema alone imported fine. Art Kagel did not recognise the sqlobj message; David Williams said sqlobj errors come from dbimport. Changing onconfig parameters did not help and the error moved around. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi! I'm trying to port an application written in 4gl to Linux. It works until I try to import the working Database which contains at most 2 GB of data. During database import I get the following message: -------------------------------------------------------------- create unique index "mbs".huelidx on "mbs".huel (jahr,kap,dr,tit,huelsi, huel,u_nr); *** execute sqlobj 212 - Cannot add index. 105 - ISAM error: bad isam file format. -------------------------------------------------------------- This error doesn't appear when importing only the core Database wihout any data. Even indexes are no problem. My Machine: Siemens Primergy 470 CPU: 1x Pentium II 400 MHz, 128 MB RAM (ECC) Mylex DAC960 RAID Controller OS: Linux kernel 2.2.12 Informix Dynamic Server Version 7.30.U Any ideas? Thanks a lot Burkhard
What import tools are you using? Sounds like dbimport, but that message:
"*** execute sqlobj" is not familiar?!?
Art S. Kagel
Burkhard Obergöker wrote:
>
> Hi!
>
> I'm trying to port an application written in 4gl to Linux. It works
> until I try to import the working Database which contains at most 2 GB
> of data. During database import I get the following message:
>
> --------------------------------------------------------------
> create unique index "mbs".huelidx on "mbs".huel (jahr,kap,dr,tit,huelsi,
> huel,u_nr);
> *** execute sqlobj
> 212 - Cannot add index.
>
> 105 - ISAM error: bad isam file format.
> --------------------------------------------------------------
>
> This error doesn't appear when importing only the core Database wihout
> any data. Even indexes are no problem.
>
> My Machine:
>
> Siemens Primergy 470
> CPU: 1x Pentium II 400 MHz, 128 MB RAM (ECC)
> Mylex DAC960 RAID Controller
>
> OS:
> Linux kernel 2.2.12
> Informix Dynamic Server Version 7.30.U
>
> Any ideas?
>
> Thanks a lot
> Burkhard
In article <38034CFB.88C811BF@bloomberg.net>, Art S. Kagel
<kagel@bloomberg.net> writes
>What import tools are you using? Sounds like dbimport, but that message:
>"*** execute sqlobj" is not familiar?!?
>
dbimport seems to prepare something called sqlobj. I guess that is the
name of the prepared statement it uses. I have seen errors with sqlobj
before and they are dbimport errors.
>Art S. Kagel
--
David Williams
"Art S. Kagel" schrieb:
>
> What import tools are you using? Sounds like dbimport, but that message:
> "*** execute sqlobj" is not familiar?!?
>
Right. I's dbimport. In detail is was this statement:
dbimport -i /opt/mbs/export -d data01 mbs
Meantime I changed various parameters in the onconfig file but without
efford. The problem appeard on different positions of the import so I
guess it's not a failure of the exported data.
Here are the important (I think) parameters of onconfig:
LOCKS 20000
BUFFERS 6000
NUMAIOVPS
PHYSBUFF 32
LOGBUFF 32LOGSMAX 200
CLEANERS 8
SHMBASE 0x10000000L
SHMVIRTSIZE 30000
SHMADD 8192
SHMTOTAL 0
CKPTINTVL 300
LRUS 8
LRU_MAX_DIRTY 60
LRU_MIN_DIRTY 50
LTXHWM 50
LTXEHWM 60
TXTIMEOUT 300
STACKSIZE 32
bye
Burkhard