Informix

Informix

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  dbexport - schema issue when using logical_char

    Posted 07/02/25 07:49 AM

    Hello,

    I currently migrated one Informix 14 database with sql_logical_char=OFF into a new database with SQL_LOGICAL_CHAR=2
    Informix successfully doubled my expressions, so it created a char(72) field, when i wrote a add column myColumn char(36)
    CLIENT/DBLOCAL = en_us.UTF8

    But now when I am exporting the database using dbexport, Informix creates the sql-commands with myColumn char(18)
    Does anyone know this issue when working with SQL_LOGICAL_CHAR or do you know how I can resolve that?

    In my eyes I need a myColumn char(36) in the genereated SQL Script, or?


    Thanks in advance

    Andre



    ------------------------------
    Andre Emmerichs
    ------------------------------


  • 2.  RE: dbexport - schema issue when using logical_char

    Posted 07/02/25 07:55 AM

    Andre:

    What is the collength value for this column in syscolumns?

    Also, I would be interested to know what dbschema -ss and my own myschema (assuming you have it installed) report for that table?

    Art



    ------------------------------
    Art S. Kagel, President and Principal Consultant
    ASK Database Management Corp.
    www.askdbmgt.com
    ------------------------------



  • 3.  RE: dbexport - schema issue when using logical_char

    Posted 07/02/25 10:05 AM

    Hey, 

    thanks for that hint, in syscolumns its only 36 and not 72...
    One database on the server was set up incorrectly, after I tried it on the other one where syscolumns said 72 the export was correct



    ------------------------------
    Andre Emmerichs
    ------------------------------

    Original Message


  • 4.  RE: dbexport - schema issue when using logical_char

    Posted 07/03/25 04:44 AM

    When SQL_LOGICAL_CHAR is used, then there is an "internal size" and an "external size"
    I mean internally it is handled as a char of size 72 and externally it is handled as a char of size 36. 
    What you see exactly where depends if you use a tool, look at internal information, .....

    When you have see a chance to edit and correct the SQL file before the dbimport (double the size of chars), then I would suggest to do this.
    To avoid any future confusion with the external and the internal size of a char. 



    ------------------------------
    Hedwig Fuchs
    ------------------------------

    Original Message


Related Content