Displaying a non existent column from a Table.

Hi
I have an SQL Query that returns back a count of all the
entities
select count(*)'COUNTER',
id_entity 'ENTITY'
from  claim 
where id_status = 'O'
group by id_status,id_entity 
order by id_entity ASC
Output
COUNTER ENTITY
169     AGL
6       DBC
28      DELI would like to put a non existent column called 'Type' with a counter
of 0,so that the output looks like :
COUNTER ENTITY
0       TYP
169     AGL
6       DBC
28      DELIs this possible ? What do I need to change in my select clause
for this?
Please help

monalalwani, do you mean something like this?
you have -
1 select count(*) as counter, deptno
2 from emp
3* group by deptno
UT1 > /
COUNTER DEPTNO
5 10
5 20
6 30
-- but want counter = 0 for dept 0
UT1 > select count(*) as counter, deptno
2 from emp
3 group by deptno
4 union
5 select 0, 00
6 from dual
7 /
COUNTER DEPTNO
0 0
5 10
5 20
6 30
HTH -- Mark D Powell --

Similar Messages

  • One can create an index on a non-existent column in a table

    I am using Oracle 10.2.0.3 on Windows 2003. I wanted to create an index on columnb of
    Tablea. When I use statement like:
    Create index index1 on tablea (‘columnb’) …
    Oracle created index: index1. However, when I looked tat the column in user_ind_columns it had some weird colculn like SYS_NCxxxx. For sometime, I had
    No idea what was going on. My index was not being used in queries at all. Then it dawned on me that I should not put single quotes around columnb. Once I removed quotes, things worked as expected.
    But why does Oracle allow index on a non-existent column?

    we cannot create the index on nonexistent column of table We can. Its called a function-based index. Here's how we do it.
    Also read Howard's reply, right above yours.
    SQL> desc t
    Name                                      Null?    Type
    OWNER                                     NOT NULL VARCHAR2(30)
    OBJECT_NAME                               NOT NULL VARCHAR2(30)
    SUBOBJECT_NAME                                     VARCHAR2(30)
    OBJECT_ID                                 NOT NULL NUMBER
    DATA_OBJECT_ID                                     NUMBER
    OBJECT_TYPE                                        VARCHAR2(19)
    CREATED                                   NOT NULL DATE
    LAST_DDL_TIME                             NOT NULL DATE
    TIMESTAMP                                          VARCHAR2(19)
    STATUS                                             VARCHAR2(7)
    TEMPORARY                                          VARCHAR2(1)
    GENERATED                                          VARCHAR2(1)
    SECONDARY                                          VARCHAR2(1)
    SQL> create index t_idx on t( substr(object_name, 1, 5));
    Index created.
    SQL> select column_name from user_ind_columns where index_name = 'T_IDX';
    COLUMN_NAME
    SYS_NC00014$
    SQL> select index_type from user_indexes where index_name = 'T_IDX';
    INDEX_TYPE
    FUNCTION-BASED NORMAL
    SQL>

  • Displaying non existing vendors from lfa1 table..

    Hi All..
    I have a selection screen range for vendor number: LIFNR.
    I want to display all the vendor numbers that are not present in the LFA1 table.. ( If the user gives the vendor range on the selection screen)..
    Any idea or suggestions on how to approach would be great..
    Thanks a lot..

    OK then , pl try thye following piece of code...
    report  zlif                                    .
    data:  w_num type i.
    data: begin of itab occurs 0,
            lifnr type lifnr,
          end of itab.
    data itab2 like itab occurs 0 with header line.
    data w_lifnr type lifnr.
    select-options: s_lifnr for w_lifnr.
    ranges: r_lifnr for w_lifnr.
    select lifnr into table itab from lfa1.
    find the number of entries
    w_num = s_lifnr-high - s_lifnr-low.
    w_num = w_num + 1.
    do w_num times.
      if sy-index = 1.
        w_lifnr = s_lifnr-low.
      else.
        w_lifnr = w_lifnr + 1.
      endif.
      r_lifnr-sign = 'I'.
      r_lifnr-option = 'EQ'.
      r_lifnr-low = w_lifnr.
      append r_lifnr.
    enddo.
    loop at r_lifnr.
      read table itab with key lifnr = r_lifnr-low.
      if sy-subrc ne 0.
        write:/ r_lifnr-low.
      endif.
    endloop.
    Regards,
    Suresh Datti

  • Evolution Calendar displays old, non-existing events from Google Calen

    I attached a screen shot of evolution calendar for an easy explanation of the issue. Most of the events on that day are repeated events which ended very long ago (i.e.they are not in the Google calendar for that particular day). Does anybody know how to tell Evolution not to show those already-ended events?
    Thanks.

    Found the bug report, here it is in Gnome Bugzilla:
    https://bugzilla.gnome.org/show_bug.cgi?id=710683

  • Columns from different tables displayed in an ADF table format

    I have a many to one relationship between 2 tables (checklist -> subcontract). I would like to display columns from each table on a web page in an ADF Read Only Table format. I created a method that returns the data I need from the tables. When I drag that method over to my page JDev I'm only allowed to select columns from either the checklist table OR the subcontract table. I need one column from the subcontract table and several columns from the checklist table. I'm using JDev 10.1.3.2 and an Oracle 11g database. Thank you in advance.
    -Wade

    Thank you for your response. I ended up creating a new getter in the Checklist table which refers to the column in the Subcontract table. Then I was able to create a table column for that returned value.
    Thanks again!
    -W

  • How to delete a column from the table control in module pool?

    Hi,
      can any one please tell How to delete a column from the table control in module pool?
    thanks in advance
    warm regards
    HareeshKumar N

    hi hareesh,
    I think it is better to hide it.
    How to hide: You can check this link
    Dynamic Hide column in table control

  • How to remove a column from alv table

    Hi All
    How to remove a specific column from alv table.?
    Thanks & Regards
    SUN

    For delete u can follow the above post..
    Fo making invisible :
    data m_col type ref to cl_salv_wd_column.
    m_col = alv_mode->IF_SALV_WD_COLUMN_SETTINGS->GET_COLUMN (' col1' ).
    m_col->SET_VISIBILITY( '01'  ).

  • How can I select columns from a table EMP, using Select statement?.

    Hi Friends,
    How can I select columns from a table EMP?.
    I want to select columns of EMP table, using select statement.
    Please reply me urgently.
    Shahzad

    Something like this:
    scott@DBA> select empno,ename,job from emp;
         EMPNO ENAME      JOB
          7369 SMITH      CLERK
          7499 ALLEN      SALESMAN
          7521 WARD       SALESMAN
          7566 JONES      MANAGER
          7654 MARTIN     SALESMAN
          7698 BLAKE      MANAGER
          7782 CLARK      MANAGER
          7788 SCOTT      ANALYST
          7839 KING       PRESIDENT
          7844 TURNER     SALESMAN
          7876 ADAMS      CLERK
          7900 JAMES      CLERK
          7902 FORD       ANALYST
          7934 MILLER     CLERK
    14 rows selected.Check the documentation:
    http://download-east.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_10002.htm#sthref9697
    Message was edited by:
    Delfino Nunez

  • Including column from fact table reduces number of rows returned

    Hello
    I am facing this issue where in a report I select 5 columns from a fact table. Out of these five columns one of the column is "Amount" for which the aggregation rule is defined as Sum in RPD.
    When I include these five column and filter results based on some criterion , I get all the rows (three rows) that satisfy the criterion. No I add a sixth column to my report and suddenly I only see one row returned by my report. Addition of this sixth column does not affect the criterion as the criterion is not based on this column. But this sixth column is a calculated column.
    I tried different things but because the report was just getting columns from one table (fact) and suddenly inclusion of one column leads to reduction in number of rows , I was unable to find any reason why would that happen.
    So I thought that some one in community may know that in what scenario this happens.
    Thanks

    Are there any repeated values? I'm wondering if what you're seeing is actually suppression of repetition in the results. Edit the analysis, go to the criteria tab, click column properties, go to the Column Format tab, and change the setting for value suppression from 'Suppress" to "Repeat". Repeat for each of your 6 columns and check the outcome.
    Otherwise, I would try testing with other calculations and also bring in some columns from dimension tables to see how this affects the result. You should be able to come up with a case-by-case scenario to work out exactly what causes the rows to be suppressed which will get us one step to closer to working out why the rows get suppressed.
    Thanks,
    George

  • Delete a column from the table

    Hi.
    I would like to delete a column from a table. I want to drop the table and recreate it later. But this table has a primary key which
    is a foreign key of other tables. So after I recreate the table I must recover the relationship of this table and other tables.
    How do I get the information about the primary key of this table as a foreign key of other tables from data dictionary?
    Thanks in advance
    null

    For ur query the reply whay u have got is correct one. For further quries similar to one u had u can download a tool named TOAD (Tools for Oracle Application Developer) from quest site (www.quest.com). Install it a proceed.
    Do let me know how and what u feek about TOAD.

  • WARN  kodo.jdbc.Schema  - Existing column "JDOID" on table

    Sorry, I've posted this before and never got back with some debug.
    I'm getting
    WARN kodo.jdbc.Schema - Existing column "JDOID" on table "<TABLE NAME
    HERE>" is incompatible with the same column in the given schema definition.
    I running
    kodo.jdbc.meta.MappingTool.main("-a","buildSchema","persistent.class(s)"...
    Here my complete trace output (Kodo 3.0.1)
    0 [23.01.04 10:04:39,712] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.alert.config.AlertConfiguration" with action
    "buildSchema".
    2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.alert.config.MonitoredInteractionType" with
    action "buildSchema".
    2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.alert.config.MonitoredSourceProcessType"
    with action "buildSchema".
    2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.alert.Alert" with action "buildSchema".
    2303 [23.01.04 10:04:42,015] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.ClientConfiguration" with
    action "buildSchema".
    2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.ClientIdentity" with action
    "buildSchema".
    2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.ConfigurationOption" with
    action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.ConfigurationValue" with
    action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.FileTrackingConfiguration"
    with action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.GeneralConfiguration" with
    action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.InteractionNotification" with
    action "buildSchema".
    2593 [23.01.04 10:04:42,305] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.NotificationType" with action
    "buildSchema".
    2603 [23.01.04 10:04:42,315] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.client.PCIdentity" with action
    "buildSchema".
    2613 [23.01.04 10:04:42,325] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.pc.PCConfiguration" with action
    "buildSchema".
    2643 [23.01.04 10:04:42,355] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.server.ConsoleAdminUser" with action
    "buildSchema".
    2693 [23.01.04 10:04:42,405] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.server.SafeArea" with action
    "buildSchema".
    2723 [23.01.04 10:04:42,435] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.server.ServerConfiguration" with
    action "buildSchema".
    2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.config.server.TemplateDefinition" with
    action "buildSchema".
    2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.connection.ConnectCommand" with action
    "buildSchema".
    2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.interaction.EntityInteraction"
    with action "buildSchema".
    2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping tool running
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionFileElement" with
    action "buildSchema".
    2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping tool running
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionFileProperty" with
    action "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionProperty" with
    action "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionSourceIdentity"
    with action "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.Entity" with action
    "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.EntityChronicle" with action
    "buildSchema".
    2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.EntityLocation" with action
    "buildSchema".
    2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.EntityLocationFilePath" with
    action "buildSchema".
    2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.EntityNode" with action
    "buildSchema".
    2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping tool running
    on type "class com.jario.server.entitymodel.EntityProperty" with action
    "buildSchema".
    2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Recording mapping and
    schema changes.
    2953 [23.01.04 10:04:42,665] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ALERT".
    2983 [23.01.04 10:04:42,695] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "alert".
    2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALERTCONFIGURATION_JDOID" on table "alert".
    2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALERTNAME" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "TYPESTR" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "TYPE_NULL" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ALERTCONFIG".
    3034 [23.01.04 10:04:42,746] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALERTGRANUALITY_NULL" on table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALERTGRANULARITYLEVEL" on table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "CLIENTNOTIFICATIONGROUP_NULL" on table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ENTITYNODE_JDOID" on table "alertconfig".
    3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "alertconfig".
    3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "alertconfig".
    3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "alertconfig".
    3064 [23.01.04 10:04:42,776] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "TYPESTR" on table "alertconfig".
    3064 [23.01.04 10:04:42,776] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ALERTCONFIG_EXTERNPROCTYPE".
    3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "EXCLUDEDSOURCEPROCESSTYP_JDOID" on table
    "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "EXCLUDEDSOURCEPROCESSTYP_ORDER" on table
    "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name
    "ALERTCONFIG_MONINTERACTTYPE".
    3084 [23.01.04 10:04:42,796] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "alertconfig_moninteracttype".
    3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "alertconfig_moninteracttype".
    3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "MONITOREDINTERACTIONTYP_JDOID" on table
    "alertconfig_moninteracttype".
    3094 [23.01.04 10:04:42,806] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "MONITOREDINTERACTIONTYP_ORDER" on table
    "alertconfig_moninteracttype".
    3094 [23.01.04 10:04:42,806] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CLIENTALERTCONFIG".
    3104 [23.01.04 10:04:42,816] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALERTTYPE" on table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "clientalertconfig".
    3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name
    "CLIENTALERTCONFIG_NOTIFYSET".
    3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientalertconfig_notifyset".
    3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "INTERACTIONNOTIFYSET_JDOID" on table "clientalertconfig_notifyset".
    3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "INTERACTIONNOTIFYSET_ORDER" on table "clientalertconfig_notifyset".
    3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientalertconfig_notifyset".
    3124 [23.01.04 10:04:42,836] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CLIENTCONFIG".
    3144 [23.01.04 10:04:42,856] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientconfig".
    3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "CLIENTIDENTITY_JDOID" on table "clientconfig".
    3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "FILETRACKINGCONFIG_JDOID" on table "clientconfig".
    3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "GENERALCONFIGURATION_JDOID" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name
    "CLIENTCONFIG_ALLALERTCONFIG".
    3184 [23.01.04 10:04:42,896] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientconfig_allalertconfig".
    3184 [23.01.04 10:04:42,896] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALLALERTSCONFIGURATION_JDOID" on table
    "clientconfig_allalertconfig".
    3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ALLALERTSCONFIGURATION_ORDER" on table
    "clientconfig_allalertconfig".
    3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientconfig_allalertconfig".
    3194 [23.01.04 10:04:42,906] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CLIENTFILETRACKINGCONFIG".
    3234 [23.01.04 10:04:42,946] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientfiletrackingconfig".
    3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "EXCLUDEDFOLDERS_JDOID" on table "clientfiletrackingconfig".
    3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "FILETYPES_JDOID" on table "clientfiletrackingconfig".
    3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "clientfiletrackingconfig".
    3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientfiletrackingconfig".
    3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "clientfiletrackingconfig".
    3244 [23.01.04 10:04:42,956] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CLIENTGENERALCONFIG".
    3264 [23.01.04 10:04:42,976] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientgeneralconfig".
    3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "clientgeneralconfig".
    3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientgeneralconfig".
    3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "clientgeneralconfig".
    3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "LANGUAGE_JDOID" on table "clientgeneralconfig".
    3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "LOADMESSENGERONSTARTUP_JDOID" on table "clientgeneralconfig".
    3284 [23.01.04 10:04:42,996] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "LOADVIEWERONSTARTUP_JDOID" on table "clientgeneralconfig".
    3284 [23.01.04 10:04:42,996] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CLIENTIDENTITY".
    3324 [23.01.04 10:04:43,036] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "clientidentity".
    3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "DOMAINSTR" on table "clientidentity".
    3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "clientidentity".
    3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "clientidentity".
    3334 [23.01.04 10:04:43,046] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "clientidentity".
    3344 [23.01.04 10:04:43,056] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "USERNAME" on table "clientidentity".
    3354 [23.01.04 10:04:43,066] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CONFIGOPTION".
    3384 [23.01.04 10:04:43,096] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "configoption".
    3384 [23.01.04 10:04:43,096] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "MANDATORY" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "SELECTED" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "VALUESTR" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CONFIGVALUE".
    3414 [23.01.04 10:04:43,126] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "LOCKED" on table "configvalue".
    3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "MULTIOPTION" on table "configvalue".
    3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "SAVEDELETEDOPTIONS" on table "configvalue".
    3434 [23.01.04 10:04:43,146] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CONFIGVALUE_DELETEOPTIONS".
    3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "DELETEDOPTIONS_JDOID" on table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "DELETEDOPTIONS_ORDER" on table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CONFIGVALUE_OPTIONS".
    3464 [23.01.04 10:04:43,176] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "configvalue_options".
    3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "configvalue_options".
    3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "OPTIONS_JDOID" on table "configvalue_options".
    3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "OPTIONS_ORDER" on table "configvalue_options".
    3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CONNECTIONCOMMAND".
    3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "connectioncommand".
    3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "connectioncommand".
    3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "connectioncommand".
    3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "connectioncommand".
    3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "SENDERSPCIDENTITY_JDOID" on table "connectioncommand".
    3484 [23.01.04 10:04:43,196] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "CONSOLEADMINUSER".
    3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "PASSWORD" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "USERNAME" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITY".
    3544 [23.01.04 10:04:43,256] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entity".
    3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ENTITYNODE_JDOID" on table "entity".
    3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "HASHCODE" on table "entity".
    3554 [23.01.04 10:04:43,266] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entity".
    3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entity".
    3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entity".
    3574 [23.01.04 10:04:43,286] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYCHRONICLE".
    3584 [23.01.04 10:04:43,296] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entitychronicle".
    3584 [23.01.04 10:04:43,296] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ROOTENTITYNODE_JDOID" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYINTER".
    3604 [23.01.04 10:04:43,316] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "EXACTTIMESTAMP" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "FILEELEMENT_JDOID" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "INTERACTIONTYPE_NULL" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "OLDFILEELEMENT_JDOID" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "SOURCEIDENTITY_JDOID" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "SOURCEPROCESSNAME" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "TIMESTAMPDATE" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "TYPESTR" on table "entityinter".
    3624 [23.01.04 10:04:43,336] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYINTERFILEELEMENT".
    3634 [23.01.04 10:04:43,346] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityinterfileelement".
    3634 [23.01.04 10:04:43,346] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "FILESTORAGETYPE_NULL" on table "entityinterfileelement".
    3644 [23.01.04 10:04:43,356] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "FULLPATH" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "HASHCODE" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "REMOTELOCALPATH" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "TYPESTR" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name
    "ENTITYINTERFILEELEMENT_ENTPROP".
    3684 [23.01.04 10:04:43,396] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityinterfileelement_entprop".
    3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ENTITYINTERACTIONPROPS_JDOID" on table
    "entityinterfileelement_entprop".
    3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ENTITYINTERACTIONPROPS_ORDER" on table
    "entityinterfileelement_entprop".
    3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityinterfileelement_entprop".
    3694 [23.01.04 10:04:43,406] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYINTERFILEPROPERTY".
    3704 [23.01.04 10:04:43,416] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityinterfileproperty".
    3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entityinterfileproperty".
    3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityinterfileproperty".
    3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entityinterfileproperty".
    3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "KEYSTR" on table "entityinterfileproperty".
    3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "VALUESTR" on table "entityinterfileproperty".
    3724 [23.01.04 10:04:43,436] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYINTERPROPERTY".
    3734 [23.01.04 10:04:43,446] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "KEYSTR" on table "entityinterproperty".
    3744 [23.01.04 10:04:43,456] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "VALUESTR" on table "entityinterproperty".
    3744 [23.01.04 10:04:43,456] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYINTERSOURCEIDENTITY".
    3754 [23.01.04 10:04:43,466] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "CLIENTIDENTITY_JDOID" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOCLASS" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOVERSION" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "PCIDENTITY_JDOID" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYINTER_ENTPROP".
    3775 [23.01.04 10:04:43,487] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entityinter_entprop".
    3775 [23.01.04 10:04:43,487] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ENTITYINTERACTIONPROPS_JDOID" on table "entityinter_entprop".
    3775 [23.01.04 10:04:43,487] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "ENTITYINTERACTIONPROPS_ORDER" on table "entityinter_entprop".
    3775 [23.01.04 10:04:43,487] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "JDOID" on table "entityinter_entprop".
    3805 [23.01.04 10:04:43,517] [main] INFO kodo.jdbc.Schema - Reading table
    information for schema name "null", table name "ENTITYLOCATION".
    3815 [23.01.04 10:04:43,527] [main] INFO kodo.jdbc.Schema - Reading column
    information for table "entitylocation".
    3815 [23.01.04 10:04:43,527] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "CREATORENTITYINTERACTION_JDOID" on table "entitylocation".
    3815 [23.01.04 10:04:43,527] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "DELETED" on table "entitylocation".
    3815 [23.01.04 10:04:43,527] [main] DEBUG kodo.jdbc.Schema - Found existing
    column "FILESTORAGETYPE_NULL" on tabl

    Any Ideas on the warns I'm getting via running
    'kodo.jdbc.meta.MappingTool.main'
    For every table I have:
    'WARN kodo.jdbc.Schema - Existing column "JDOID" on table "<TABLE NAME
    HERE>" is incompatible with the same column in the given schema definition.'
    Kind Regards
    Graham Cruickshanks
    (Now running Kodo 3.0.2)
    "Graham Cruickshanks" <[email protected]> wrote in message
    news:[email protected]...
    Sorry, I've posted this before and never got back with some debug.
    I'm getting
    WARN kodo.jdbc.Schema - Existing column "JDOID" on table "<TABLE NAME
    HERE>" is incompatible with the same column in the given schemadefinition.
    >
    I running
    kodo.jdbc.meta.MappingTool.main("-a","buildSchema","persistent.class(s)"...
    >
    Here my complete trace output (Kodo 3.0.1)
    0 [23.01.04 10:04:39,712] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.alert.config.AlertConfiguration" withaction
    "buildSchema".
    2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.alert.config.MonitoredInteractionType"with
    action "buildSchema".
    2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.alert.config.MonitoredSourceProcessType"
    with action "buildSchema".
    2253 [23.01.04 10:04:41,965] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.alert.Alert" with action "buildSchema".
    2303 [23.01.04 10:04:42,015] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.ClientConfiguration" with
    action "buildSchema".
    2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.ClientIdentity" with action
    "buildSchema".
    2573 [23.01.04 10:04:42,285] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.ConfigurationOption" with
    action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.ConfigurationValue" with
    action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.FileTrackingConfiguration"
    with action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.GeneralConfiguration" with
    action "buildSchema".
    2583 [23.01.04 10:04:42,295] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.InteractionNotification"with
    action "buildSchema".
    2593 [23.01.04 10:04:42,305] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.NotificationType" withaction
    "buildSchema".
    2603 [23.01.04 10:04:42,315] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.client.PCIdentity" with action
    "buildSchema".
    2613 [23.01.04 10:04:42,325] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.pc.PCConfiguration" with action
    "buildSchema".
    2643 [23.01.04 10:04:42,355] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.server.ConsoleAdminUser" withaction
    "buildSchema".
    2693 [23.01.04 10:04:42,405] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.server.SafeArea" with action
    "buildSchema".
    2723 [23.01.04 10:04:42,435] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.server.ServerConfiguration" with
    action "buildSchema".
    2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.config.server.TemplateDefinition" with
    action "buildSchema".
    2813 [23.01.04 10:04:42,525] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.connection.ConnectCommand" with action
    "buildSchema".
    2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.interaction.EntityInteraction"
    with action "buildSchema".
    2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionFileElement"with
    action "buildSchema".
    2863 [23.01.04 10:04:42,575] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionFileProperty"with
    action "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionProperty" with
    action "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class
    com.jario.server.entitymodel.interaction.EntityInteractionSourceIdentity"
    with action "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.Entity" with action
    "buildSchema".
    2873 [23.01.04 10:04:42,585] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.EntityChronicle" with action
    "buildSchema".
    2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.EntityLocation" with action
    "buildSchema".
    2883 [23.01.04 10:04:42,595] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.EntityLocationFilePath" with
    action "buildSchema".
    2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.EntityNode" with action
    "buildSchema".
    2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Mapping toolrunning
    on type "class com.jario.server.entitymodel.EntityProperty" with action
    "buildSchema".
    2903 [23.01.04 10:04:42,615] [main] INFO kodo.Tool - Recording mappingand
    schema changes.
    2953 [23.01.04 10:04:42,665] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ALERT".
    2983 [23.01.04 10:04:42,695] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "alert".
    2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALERTCONFIGURATION_JDOID" on table "alert".
    2983 [23.01.04 10:04:42,695] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALERTNAME" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "TYPESTR" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "TYPE_NULL" on table "alert".
    2993 [23.01.04 10:04:42,705] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ALERTCONFIG".
    3034 [23.01.04 10:04:42,746] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALERTGRANUALITY_NULL" on table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALERTGRANULARITYLEVEL" on table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "CLIENTNOTIFICATIONGROUP_NULL" on table "alertconfig".
    3044 [23.01.04 10:04:42,756] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ENTITYNODE_JDOID" on table "alertconfig".
    3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "alertconfig".
    3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "alertconfig".
    3054 [23.01.04 10:04:42,766] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "alertconfig".
    3064 [23.01.04 10:04:42,776] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "TYPESTR" on table "alertconfig".
    3064 [23.01.04 10:04:42,776] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name"ALERTCONFIG_EXTERNPROCTYPE".
    >
    3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "EXCLUDEDSOURCEPROCESSTYP_JDOID" on table
    "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "EXCLUDEDSOURCEPROCESSTYP_ORDER" on table
    "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "alertconfig_externproctype".
    3074 [23.01.04 10:04:42,786] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name
    "ALERTCONFIG_MONINTERACTTYPE".
    3084 [23.01.04 10:04:42,796] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "alertconfig_moninteracttype".
    3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "alertconfig_moninteracttype".
    3084 [23.01.04 10:04:42,796] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "MONITOREDINTERACTIONTYP_JDOID" on table
    "alertconfig_moninteracttype".
    3094 [23.01.04 10:04:42,806] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "MONITOREDINTERACTIONTYP_ORDER" on table
    "alertconfig_moninteracttype".
    3094 [23.01.04 10:04:42,806] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CLIENTALERTCONFIG".
    3104 [23.01.04 10:04:42,816] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALERTTYPE" on table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientalertconfig".
    3104 [23.01.04 10:04:42,816] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "clientalertconfig".
    3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name
    "CLIENTALERTCONFIG_NOTIFYSET".
    3114 [23.01.04 10:04:42,826] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientalertconfig_notifyset".
    3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "INTERACTIONNOTIFYSET_JDOID" on table"clientalertconfig_notifyset".
    >
    3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "INTERACTIONNOTIFYSET_ORDER" on table"clientalertconfig_notifyset".
    >
    3124 [23.01.04 10:04:42,836] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientalertconfig_notifyset".
    3124 [23.01.04 10:04:42,836] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CLIENTCONFIG".
    3144 [23.01.04 10:04:42,856] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientconfig".
    3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "CLIENTIDENTITY_JDOID" on table "clientconfig".
    3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "FILETRACKINGCONFIG_JDOID" on table "clientconfig".
    3154 [23.01.04 10:04:42,866] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "GENERALCONFIGURATION_JDOID" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "clientconfig".
    3164 [23.01.04 10:04:42,876] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name
    "CLIENTCONFIG_ALLALERTCONFIG".
    3184 [23.01.04 10:04:42,896] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientconfig_allalertconfig".
    3184 [23.01.04 10:04:42,896] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALLALERTSCONFIGURATION_JDOID" on table
    "clientconfig_allalertconfig".
    3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ALLALERTSCONFIGURATION_ORDER" on table
    "clientconfig_allalertconfig".
    3194 [23.01.04 10:04:42,906] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientconfig_allalertconfig".
    3194 [23.01.04 10:04:42,906] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CLIENTFILETRACKINGCONFIG".
    3234 [23.01.04 10:04:42,946] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientfiletrackingconfig".
    3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "EXCLUDEDFOLDERS_JDOID" on table "clientfiletrackingconfig".
    3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "FILETYPES_JDOID" on table "clientfiletrackingconfig".
    3234 [23.01.04 10:04:42,946] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "clientfiletrackingconfig".
    3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientfiletrackingconfig".
    3244 [23.01.04 10:04:42,956] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "clientfiletrackingconfig".
    3244 [23.01.04 10:04:42,956] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CLIENTGENERALCONFIG".
    3264 [23.01.04 10:04:42,976] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientgeneralconfig".
    3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "clientgeneralconfig".
    3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientgeneralconfig".
    3264 [23.01.04 10:04:42,976] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "clientgeneralconfig".
    3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "LANGUAGE_JDOID" on table "clientgeneralconfig".
    3274 [23.01.04 10:04:42,986] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "LOADMESSENGERONSTARTUP_JDOID" on table "clientgeneralconfig".
    3284 [23.01.04 10:04:42,996] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "LOADVIEWERONSTARTUP_JDOID" on table "clientgeneralconfig".
    3284 [23.01.04 10:04:42,996] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CLIENTIDENTITY".
    3324 [23.01.04 10:04:43,036] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "clientidentity".
    3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "DOMAINSTR" on table "clientidentity".
    3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "clientidentity".
    3324 [23.01.04 10:04:43,036] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "clientidentity".
    3334 [23.01.04 10:04:43,046] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "clientidentity".
    3344 [23.01.04 10:04:43,056] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "USERNAME" on table "clientidentity".
    3354 [23.01.04 10:04:43,066] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CONFIGOPTION".
    3384 [23.01.04 10:04:43,096] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "configoption".
    3384 [23.01.04 10:04:43,096] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "MANDATORY" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "SELECTED" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "VALUESTR" on table "configoption".
    3394 [23.01.04 10:04:43,106] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CONFIGVALUE".
    3414 [23.01.04 10:04:43,126] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "configvalue".
    3424 [23.01.04 10:04:43,136] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "LOCKED" on table "configvalue".
    3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "MULTIOPTION" on table "configvalue".
    3434 [23.01.04 10:04:43,146] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "SAVEDELETEDOPTIONS" on table "configvalue".
    3434 [23.01.04 10:04:43,146] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name"CONFIGVALUE_DELETEOPTIONS".
    >
    3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "DELETEDOPTIONS_JDOID" on table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "DELETEDOPTIONS_ORDER" on table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "configvalue_deleteoptions".
    3454 [23.01.04 10:04:43,166] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CONFIGVALUE_OPTIONS".
    3464 [23.01.04 10:04:43,176] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "configvalue_options".
    3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "configvalue_options".
    3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "OPTIONS_JDOID" on table "configvalue_options".
    3464 [23.01.04 10:04:43,176] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "OPTIONS_ORDER" on table "configvalue_options".
    3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CONNECTIONCOMMAND".
    3474 [23.01.04 10:04:43,186] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "connectioncommand".
    3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "connectioncommand".
    3474 [23.01.04 10:04:43,186] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "connectioncommand".
    3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "connectioncommand".
    3484 [23.01.04 10:04:43,196] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "SENDERSPCIDENTITY_JDOID" on table "connectioncommand".
    3484 [23.01.04 10:04:43,196] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "CONSOLEADMINUSER".
    3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "PASSWORD" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "USERNAME" on table "consoleadminuser".
    3494 [23.01.04 10:04:43,206] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ENTITY".
    3544 [23.01.04 10:04:43,256] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entity".
    3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ENTITYNODE_JDOID" on table "entity".
    3544 [23.01.04 10:04:43,256] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "HASHCODE" on table "entity".
    3554 [23.01.04 10:04:43,266] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entity".
    3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entity".
    3564 [23.01.04 10:04:43,276] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "entity".
    3574 [23.01.04 10:04:43,286] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ENTITYCHRONICLE".
    3584 [23.01.04 10:04:43,296] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entitychronicle".
    3584 [23.01.04 10:04:43,296] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ROOTENTITYNODE_JDOID" on table "entitychronicle".
    3594 [23.01.04 10:04:43,306] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ENTITYINTER".
    3604 [23.01.04 10:04:43,316] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "EXACTTIMESTAMP" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "FILEELEMENT_JDOID" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "INTERACTIONTYPE_NULL" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "entityinter".
    3604 [23.01.04 10:04:43,316] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "OLDFILEELEMENT_JDOID" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "SOURCEIDENTITY_JDOID" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "SOURCEPROCESSNAME" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "TIMESTAMPDATE" on table "entityinter".
    3614 [23.01.04 10:04:43,326] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "TYPESTR" on table "entityinter".
    3624 [23.01.04 10:04:43,336] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ENTITYINTERFILEELEMENT".
    3634 [23.01.04 10:04:43,346] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entityinterfileelement".
    3634 [23.01.04 10:04:43,346] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "FILESTORAGETYPE_NULL" on table "entityinterfileelement".
    3644 [23.01.04 10:04:43,356] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "FULLPATH" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "HASHCODE" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "REMOTELOCALPATH" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "TYPESTR" on table "entityinterfileelement".
    3674 [23.01.04 10:04:43,386] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name
    "ENTITYINTERFILEELEMENT_ENTPROP".
    3684 [23.01.04 10:04:43,396] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entityinterfileelement_entprop".
    3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ENTITYINTERACTIONPROPS_JDOID" on table
    "entityinterfileelement_entprop".
    3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "ENTITYINTERACTIONPROPS_ORDER" on table
    "entityinterfileelement_entprop".
    3684 [23.01.04 10:04:43,396] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entityinterfileelement_entprop".
    3694 [23.01.04 10:04:43,406] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ENTITYINTERFILEPROPERTY".
    3704 [23.01.04 10:04:43,416] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entityinterfileproperty".
    3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entityinterfileproperty".
    3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entityinterfileproperty".
    3714 [23.01.04 10:04:43,426] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "entityinterfileproperty".
    3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "KEYSTR" on table "entityinterfileproperty".
    3724 [23.01.04 10:04:43,436] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "VALUESTR" on table "entityinterfileproperty".
    3724 [23.01.04 10:04:43,436] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name "ENTITYINTERPROPERTY".
    3734 [23.01.04 10:04:43,446] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOVERSION" on table "entityinterproperty".
    3734 [23.01.04 10:04:43,446] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "KEYSTR" on table "entityinterproperty".
    3744 [23.01.04 10:04:43,456] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "VALUESTR" on table "entityinterproperty".
    3744 [23.01.04 10:04:43,456] [main] INFO kodo.jdbc.Schema - Readingtable
    information for schema name "null", table name"ENTITYINTERSOURCEIDENTITY".
    >
    3754 [23.01.04 10:04:43,466] [main] INFO kodo.jdbc.Schema - Readingcolumn
    information for table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "CLIENTIDENTITY_JDOID" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOCLASS" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DEBUG kodo.jdbc.Schema - Foundexisting
    column "JDOID" on table "entityintersourceidentity".
    3765 [23.01.04 10:04:43,477] [main] DE

  • Selecting columns from two table is slow but same

    I am selecting 27 columns from two tables
    which running for more than 30 minutes. but
    if I select count(*) with the same query
    except the columns it is coming in seconds.
    Where is the error?

    If you post
    1) The table definitions for the underlying tables
    2) The indexes that are on the tables
    3) The two SQL statements you're running
    4) The explain plan for both statements
    we can probably be of some assistance.
    My guess is that the count(*) is able to return much more quickly because the optimizer is able to use a significantly faster query plan that is based on an index which the longer-running query cannot utilize. Without the information I've requested, though, it's hard to do more than speculate.
    Justin
    Distributed Database Consulting, Inc.
    http://www.ddbcinc.com/askDDBC

  • Update data provider queryspecification wiith columns from multiple tables

    Hi
    I have scenario like I need  updated a queryspecificaiton with columns from multiple tables
    1. Ex:
      <bOQuery name="Query">
              <resultObjects identifier="DS0.DO1" name="A$Application_ID"/>
              <resultObjects identifier="DS0.DO2" name="A$Column_Name"/>
    A$Application_ID is from Table A and A$Column_Name from table B
    The query is not adding to dataprovier when I am trying to updated from REST API.
    Please help me.
    Thanks
    Kalyan

    Have a look at the Business Intelligence platform RESTful Web Service Developer Guide, section 3.4.7 (p. 197) - Report structure: getting and updating the structure (specifications) of a report, may be a good place to start(?). Also see KBA 1952419 - How to update the properties of a web intelligence report using RESTful web service SDK .
    - Ludek
    Senior Support Engineer AGS Product Support, Global Support Center Canada
    Follow us on Twitter

  • Combining the same column from 2 tables with distinct result.

    I have 2 tables with identical name columns. One is current people and the other is historical people. I want a select that returns any name that is in either table. I want each name listed only once. I want to see 1 entry for each name if it is in the current table, the historical table, or both tables. I can easily do a select distinct on each table but how do I join the queries to get 1 result set with no duplicates? The name column is not a key field and I don't want any other columns from either table.

    Just a simple UNION:
    select name
      from current
    union
    select name
      from historical;

  • Update with Select from a non-existant column

    Hello,
    If I have two tables in Oracle database:
    Table_1 has column id, c1, c2
    Table_2 has column id, c1, c2
    If I run the following select statement, it will give error, because column c3 does not exist:
    select c3 from table_2;
    However, if I run the following update statement, it run successfully with error. It shows, for example, 10 rows updated:
    update table_1 t1 set t1.c2 =
    (select t2.c3 from table_2 t2
    where t2.id = t1.id);
    Could someone explain to me what happens?
    Regards!

    rp0428 wrote:
    >
    It's called a Correlated Sub-Query . It's documented, with examples, in the SQL Language manual
    >
    I'm familiar with correlated sub-queries. That link has NO examples using a column in the FROM list of a sub-query that is NOT in a table in the FROM list of that sub-query.
    You can certainly use constants, or functions in a select list without needing a table reference but I haven't seen any documentation showing an example of selecting a column in a sub-query that doesn't exist in one of the FROM tables.There are no examples of selecting a column from the outer query in a sub-query because in 99.999% of the cases it would be the wrong thing to do, however it is possible. Clearly the sub-query can "see" columns in the outer query otherwise how would it see the values for a correlated sub-query. As Frank said, there is nothing in the documenation that precludes using an outer column in the sub-query, and this paragraph from Frank's link certainly seems to pretty generally refer to the entire sub-query:
    If columns in a subquery have the same name as columns in the containing statement, then you must prefix any reference to the column of the table from the containing statement with the table name or alias. To make your statements easier to read, always qualify the columns in a subquery with the name or alias of the table, view, or materialized view.John

Maybe you are looking for

  • IPod touch 3g will not wifi sync... why?

    I recently updated to iOS5, not without its hassles, I might add. I now have 2 major problems. The first one is whatever I do, I cannot wirelessly sync my iPod touch 3g... even though I've reinstalled iTunes (verison 10.5.0.142) and Bonjour too... an

  • HDMI to VGA for apple TV

    I have a Proscan 4:3 TV that has a VGA input that I have used in the past. For AppleTV I am using component input now and It works fine at 480i, albeit with lower quality than I would like. Does anyone think that there is a way to get the 1080i throu

  • Moving 2 different movieClips at same time onPress function

    Hello, Im using the following code to simulate a volume control bar filling on vol+ and unfilling on vol-. The dragger is a mask that causes the fill to appear and dissappear when the mouse is pressed and dragged on the volume controller. It works we

  • Can't achieve 10MS/s with 6115 using VC++

    I have a PXI-6115, and I am trying to sample two channels simultaneously at 10MS/s. I only need about 50k samples per channel. I've attached the code I am using. It works fine up to 5MS/s, but if I try to put in a value larger than than, it ignores t

  • Ical invitations not showing up in ical

    ical invitations are not shwoing up in ical on mac or on ipad.