Uniface User Forum

 View Only

  • 1.  ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format

    Posted 06-11-2024 10:23

    Hello all,

    We are using the Uniface 10.3 and 10.4 IDE Utilities to build Deployment Archives for patches of our application. The Uniface Repository is kept in an Oracle Database. Since we has installed the latest patch (Rocket Uniface 10.4.02-050) the Deployment Archive tool is having problems. The error ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format is shown. The expected storage format is not the same as the actual storage format. Changing the storage format from VARCHAR2 to CHAR for the UDESCR field in the table does not help. The same message occurs again. (See below).

    We were able to fill out the forms, but we were not able to create the actual UAR. It also happened that both forms were empty and no new definition could be created with the same name. When we looked in the database the information about the archives are available in the tables.

    Has anyone seen the same?

    From the logfile:

    [startup] ======================================================================
    [startup] Date/time : 2024-06-07 16:25:59.36
    [startup] Uniface   : [MSW] 10.4.02.050, 050 (May 29 2024), $ioprint=0
    [startup] Command   : "Uniface\uniface104\common\bin\ide.exe" /adm=..\adm ?, pid=16440
    [startup] Asn File  : ..\adm\ide.asn
    [startup] Directory : .\wrk\
    [startup] OS        : Windows 10  (Build 19045)
    [startup] Processor : Intel64 Family 6 Model 85 Stepping 7, Intel(R) Xeon(R) Gold 6248R CPU @ 3.00GHz, 16383 Mb
    [startup] Hostname  : <hostname>
    [startup] User      : richard de vries
    [startup] ======================================================================
    2024-06-07 16:25:59.36 - Uniface session started
    I/O function: O, mode: 0, on file/table: UARCHIVE
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHIVE, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHIVE
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHIVE, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 1, on file/table: UARCHIVE
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHIVE, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    7702 - 1 objects (type: Entity Descriptor) added/updated.
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    I/O function: O, mode: 1, on file/table: UARCHIVE
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHIVE, Column UDESCR, expected storage format CHAR, actual storage format is VARCHAR2
    7702 - 6 objects (type: Form) added/updated.
    1805 - Store successful.
    7702 - 6 objects (type: Form) added/updated.
    7741 - 7 objects have been checked.
    1723 - Database not modified; store not executed.
    7702 - 1 objects (type: Form) added/updated.
    7701 - Adding/updating object (type: Form) 10 out of 13...
    1805 - Store successful.
    7702 - 13 objects (type: Form) added/updated.
    1805 - Store successful.
    7702 - 8 objects (type: Service) added/updated.
    7741 - 27 objects have been checked.
    1805 - Store successful.
    7741 - 27 objects have been checked.
    1805 - Store successful.
    I/O function: O, mode: 0, on file/table: UARCHIVE
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHIVE, Column UDESCR, expected storage format VARCHAR2, actual storage format is CHAR
    1723 - Database not modified; store not executed.
    I/O function: O, mode: 0, on file/table: UARCHITEM
    ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format: Table UARCHITEM, Column UDESCR, expected storage format VARCHAR2, actual storage format is CHAR
    7723 - Creation of deployment archive successful, 0 object(s) have been added.
    1723 - Database not modified; store not executed.
    2024-06-07 17:27:46.21 - Uniface session stopped



    ------------------------------
    Richard de Vries
    Developer
    Waard Verzekeringen BV
    Wognum NL
    ------------------------------


  • 2.  RE: ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format

    Posted 06-12-2024 03:21

    Hello Richard

    UARCHIVE.UARDEPLOY and UARCHITEM.UARDEPLOY have not changed.

    The field UDESCR is a W64 field.

    With standard connector options for Oracle it should be NCHAR(64)

    unless the setting 

    $WIDE_CHAR_BEHAVIOR = Char 

    is used

    A reason could be that the connector option fv has been added

    or an old Uniface Nine definition is picked via [RESOURCES].

     

    With $ioprint=255 you can look in the log at settings and definitions used.



    ------------------------------
    Peter Beugel
    Rocket Internal - All Brands
    Amsterdam NL
    ------------------------------

    Original Message


  • 3.  RE: ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format

    Posted 06-12-2024 04:18
    Edited by Richard de Vries 06-12-2024 08:19

    Hello Peter,

    I have run the IDE with the $ioprint=225  option. I have attached the created log. 

    The following ASN settings are used:

    [DRIVER_SETTINGS]
    ORA               = U7.3
    USYS$ORA_PARAMS   = dpa,dhfr,u4_compatibility,use_timestamp

    [RESOURCES]
    usys:ide.uar
    usys:ide_messages.uar
    usys:ide_classic.uar
    ;;uarchive functionaliteit
    ..\uar\ADDITIONS.uar

    The definition of the tables in the database:

      CREATE TABLE "UARCHIVE" 
       ( "U_ARCHNAME" CHAR(60 BYTE), 
    "UTIMESTAMP" DATE, 
    "UKVERSION" NUMBER(7,0), 
    "UMVERSION" NUMBER(7,0), 
    "UDESCR" NCHAR(64), 
    "U_SIG" CHAR(1 BYTE), 
    "U_HTS" CHAR(1 BYTE), 
    "UCOMMENT" LONG
       )
      CREATE TABLE "UARCHITEM" 
       ( "UTIMESTAMP" DATE, 
    "U_OBJNAME" VARCHAR2(255 BYTE), 
    "U_OBJTYPE" CHAR(3 BYTE), 
    "U_OBJLAN" CHAR(3 BYTE), 
    "U_ARCHNAME" CHAR(60 BYTE), 
    "U_OBJMODLIB" CHAR(60 BYTE), 
    "U_GLYPHCLASS" VARCHAR2(8 BYTE), 
    "UKVERSION" NUMBER(7,0), 
    "UMVERSION" NUMBER(7,0), 
    "UDESCR" NCHAR(64), 
    "U_BINASC" VARCHAR2(1 BYTE), 
    "U_DESTINATION" LONG
       )

    I was able to use the tool before the installation of the patch Rocket Uniface 10.4.02-050. This was done with the patch Rocket Uniface 10.4.02-049, the same ASN-files and the same database (settings).

    Could the order in the resources be the cause of the problem?

    Update:

    On the page Uniface 10.3 and 10.4 IDE Utilities the uploaded file for Uniface IDE Utilities for 10.4.zip has been uploaded on Feb 2nd, 2023. The latest update of the page itself is of May 2nd, 2023, with are history update of May 2, 2023: Uniface 10.4 IDE Utilities: Resolved problem in Deployment Archive tool when trying to add Global Variables to archive. It looks like the latest changes have not been added to the ZIP-file.

    ------------------------------
    Richard de Vries
    Developer
    Waard Verzekeringen BV
    Wognum NL
    ------------------------------

    Original Message


  • 4.  RE: ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format

    Posted 06-12-2024 09:02

    There are no changes in patch 050 that are related:

    https://community.rocketsoftware.com/discussion/rocket-uniface-10402-050-released

    One can not upload log files in this forum.

    Was moving from patch 049 to 050 really the only change ?

    You could do a test without Oracle for example with 049 and SLE and next move to 050.

    The [RESOURCES] are used to get the entity definition 

    With $ioprint=255 you should see in the log where the IDE gets the entity descriptor.

    Can you else log a case via our support portal.



    ------------------------------
    Peter Beugel
    Rocket Internal - All Brands
    Amsterdam NL
    ------------------------------

    Original Message


  • 5.  RE: ORACLE Driver Error [-80]: Column has incorrect ORACLE storage format

    Posted 06-12-2024 11:04
      |   view attached

    I hope the file will be attached now. 

    Was moving from patch 049 to 050 really the only change ? 

    Yes. I had created an archive before I did the patching to 050.

    I have tried with SLE and 050 to create the same UAR and this went ok. I did make an export for the repository in Oracle and imported it in a SLE database. I also have restore the 049 patch for using it with the Oracle repository.  The same error occured. 

    I also have drop the tables used by the tool both thru statements directly on the database server as by the SQL functionality within the IDE via the path $IDF. After both I tried to create the UARs which was still failing.



    ------------------------------
    Richard de Vries
    Developer
    Waard Verzekeringen BV
    Wognum NL
    ------------------------------

    Attachment(s)

    txt
    ide_13152.txt   1.23 MB 1 version
    Original Message