Load Definition with Oracle

Author: thomas.young@young-consulting.de (Thomas.Young)

Hi Everyone,

I am wondering if someone has a similar problem and maybe a solution.

We have Uniface Repository in Ora 11 with CLOB Fields.

Load-Definition is based on View with a LONG Datatype but that can't be read by LOAD DEFINITION function within Uniface.

We've got follow error-msg:

6859 - Unknown data type  for field .ACTIVITY.
I/O function: F, mode: 0, on file/table: USER_TAB_COLUMNS index: 1 =
ORA-00932: Inkonsistente Datentypen: %s erwartet, %s erhalten
ORACLE Driver Error [-35]: Fetch driver function failed.

We can't use u4compatibillity because than all other definitions in the repository (CLOB) don't match.

Best regards



  1. Hi Thomas,

    pls. give me a call to discuss this, think I got some answer, Uli

    Author: ulrich-merkel (ulrichmerkel@web.de)
  2. One option if you're licensed for PolyServer might be to chain UServers (with the second USERVER using the compatibility switch to read the offending table). Alternatively you could access is via the "SQL" command. I suspect one of thse might be Ulrich's solution, in which case happy to let him elaborate if necessary.

    Kind Regards,

    David Akerman
    p.s. this isn't any kind of official Compuware response (I work for UK Uniface services), just a quick brain dump in case it helps.


    Author: dakerman (david.akerman@compuware.com)
  3. This is a hint we got from the Uniface support:


    Load definitions does work but one has to use the connector option u4_compatibility.

    This is explained in the Oracle connector guide in the Uniface library.

    If this is not compatible with your Oracle repository you can do what I do here:

    Use a separate environment to load definitions (SEQ as repository) , export these definitions and import in your regular development.

    These separation can also have it’s advantages.





    Author: leibig (markus.leibig@hanic.de)
  4. Hi,

    thanks for your hints. I believe we will try the seq/ora combination.

    Best Regards


    Author: Thomas.Young (thomas.young@young-consulting.de)