IDF 9.7 Installation

Author: lalitpct@gmail.com (lalitpct)

I installed IDF for 9.7 but while connecting from IDF  9.7 to Solid database , I get the message that some of the uniface related tables are missing. Last time while 9.6 installation I used to get a message to create default tables while conneting to solid in case tables were not there. Do I need to do some additional steps for 9.7??

IDF logs=================================Connection and database information :
------------------------------------------------
    Solid client         : socw3245.dll 04.50.0022
    Solid server         : Solid Database Engine 04.50.0022
    Database name        : GUI97
    User name            : GUI97

I/O function: O, mode: 0, on file/table: UDICVER
    field  -> UDICVER          pos 0 len 0 0 type G0 G  pack 73 scalfmt 1 csfmt 0 dbfmt 0 index 0
    field  -> VERSNAME         pos 0 len 16 0 type S1 S  pack 0 scalfmt 0 csfmt 0 dbfmt 0 index 1
    field  -> VERSTYPE         pos 17 len 1 0 type S1 S  pack 0 scalfmt 0 csfmt 0 dbfmt 0 index 1
    field  -> UDESCR           pos 19 len 25 0 type S1 S  pack 0 scalfmt 0 csfmt 0 dbfmt 0 index 0
    field  -> UTIMESTAMP       pos 45 len 16 0 type E1 E  pack 0 scalfmt 0 csfmt 115 dbfmt 125 index 0
    index  - > 1.1-1 field  VERSNAME
    index  - > 1.2-1 field  VERSTYPE
select UDICVER, DICVER from UDICVER where 1=0
I/O function: O, mode: 0, on file/table: UDICVER
    field  -> UDICVER          pos 0 len 0 0 type G0 G  pack 73 scalfmt 1 csfmt 0 dbfmt 0 index 0
    field  -> VERSNAME         pos 0 len 16 0 type S1 S  pack 0 scalfmt 0 csfmt 0 dbfmt 0 index 1
    field  -> VERSTYPE         pos 17 len 1 0 type S1 S  pack 0 scalfmt 0 csfmt 0 dbfmt 0 index 1
    field  -> UDESCR           pos 19 len 25 0 type S1 S  pack 0 scalfmt 0 csfmt 0 dbfmt 0 index 0
    field  -> UTIMESTAMP       pos 45 len 16 0 type E1 E  pack 0 scalfmt 0 csfmt 115 dbfmt 125 index 0
    index  - > 1.1-1 field  VERSNAME
    index  - > 1.2-1 field  VERSTYPE
SOLID Table Error 13011: Table UDICVER does not exist
I/O function: O, mode: 0, on file/table: UCSCH

3 Comments

  1. Hi lalit In every distribution, there is a directory called "uniface\sql" For solid under 9.7 you have to/could execute sol4xdt1.sql But it is strange if you don't have UDICVER. This table is needed since years :-) Ingo --- sol4xdt1.sql   --- -- Only UDICVER (there are much more) create table UDICVER (  VERSNAME char(16) not null,  VERSTYPE char(1) not null,  UDESCR char(25) null,  UTIMESTAMP timestamp null,  primary key  (VERSNAME,VERSTYPE) );


    Author: istiller (i2stiller@gmx.de)
  2. Hi Lalit,

    The connectors for file-based databases like SQLite (SLE), Microsoft SQL Server Mobile (MSM) and EDB Embedded Database (EDB) have the 'create db =on | off' option. The Solid connector does not have this option (as Solid is not really a single-file database I presume). Another connector option I'm thinking of is the  'checks : enabled |disabled' or (synonym) 'checkschecks : on | off ' option. The default value (if not specified) for this one is the 'on' position. This connector option (in the 'on' or default behaviour) will lead to creation of tables 'on the fly'. Having said that I'm still convinced that actually creating the repository tables (and perhaps stored procedures) through the scripts in the Uniface installation directory, like Ingo describes, is to considered to be Best Practice. I've always done it this way at customer sites when using Oracle, Sybase etc. And perhaps a superfluous remark: Please do not try to connect a Uniface 9.7 installation to an existing 9.6 repository. Instead create an empty 9.7 repository, load the defaults, do an export from the 9.6 repository (defaults excluded!) and import in the empty 9.7 repository.

    Cheers, Arjen

       


    Author: Arjen van Vliet (arjen.van.vliet@uniface.com)
  3. Hi Lalit, The log that you posted only shows the part where Uniface tries to read the UDICVER table. Only after the read fails it will/should assume that it does not exist, and automatically try to create the table. Can you please share the next bit of the log? Theo.


    Author: Theo Neeskens (tneeskens@itblockz.nl)