Crash in Art-s dbcopy
Posted in 2008
Topics: Data Types & Schema Design, Migration, Import/Export & Data Conversion, Platform-Specific Issues
I-m migration a database from Solaris 2.8 9.40FC5 to Suse 11.50FC1 using Art's dbcopy program. It crashes on every table that has a lvarchar-column with "code -1831". I can-t even find this error-code ... All other tables work fine. Has anyone successfully transferred tables with lvarchars and dbcopy? Or an idea what might causing the crash? Thanks Dirk
It would seem to be a bug in the ESQL/C library or IDS itself. I have just
finished extensive testing. Dbcopy works fine for LVARCHAR columns as long
as the length of the column is 6,546 bytes or less. I was sure that I'd
tested LVARCHARs when I added support for them 8-). I will open a case with
IBM on Monday to track this. Thanks for reporting it Dirk.
Note from 6547 bytes to about 10,000 bytes dbschema gets the undocumented
error -1831. From about 10,000 bytes and up it does SEGV while fetching the
first row, but that may just be a more severe symptom of the same bug.
Art
On Sun, Aug 17, 2008 at 12:50 PM, Dirk B. <tohoNOSPAM@myrealbox.com> wrote:
> I-m migration a database from Solaris 2.8 9.40FC5 to Suse 11.50FC1 using
> Art's dbcopy program. It crashes on every table that has a
> lvarchar-column with "code -1831". I can-t even find this error-code ...
> All other tables work fine.
> Has anyone successfully transferred tables with lvarchars and dbcopy?
> Or an idea what might causing the crash?
>
> Thanks
>
> Dirk
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do those
opinions reflect those of other individuals affiliated with any entity with
which I am affiliated nor those of the entities themselves.
Art, i don-t understand the rowsize calculation of dbcopy.
A simple table like this:
create table "informix".tab1
(
tb1_id serial not null ,
tb1_tb3_id integer not null
}
I would expect 8 as the rowsize but dbcopy says 16. But table is copied
without problems.
On this one with lvarchars:
create table "informix".tab2
(
tb2_id serial not null ,
tb2_tb4_id integer not null ,
tb2_line_no integer,
tb2_retcode smallint not null ,
tb2_line lvarchar not null ,
tb2_more_info lvarchar,
tb2_man_id integer not null ,
tb2_grp_eig integer not null ,
tb2_mar_crea integer not null ,
tb2_crea_dat datetime year to second not null ,
tb2_mar_upd integer not null ,
tb2_upd_dat datetime year to second not null
)
dbschema says 4148, dbcopy 4218. And this one crashes with -1831.
Or is the rowsize that dbcopy calculates the regular rowsize + something?
Dirk