Schema.Table.Column.. a problem?

In Oracle 8.1.7.4.1:
SQL> create table trial ( a number);
Table created.
SQL> insert into trial (a) values (10);
1 row created.
SQL> commit;
Commit complete.
SQL> select sysadm.trial.a from trial;
select sysadm.trial.a from trial
ERROR at line 1:
ORA-00904: invalid column name
SQL> select sysadm.trial.a from sysadm.trial;
A
10
SQL> select trial.a from trial;
A
10
SQL> select trial.a from sysadm.trial;
A
10
SQL> show user
USER is "SYSADM"
Question:
>>>>>>
SQL> select sysadm.trial.a from trial;
>>>>>>
Why does this select fail even when I am firing the statement with the same database USER?

SELECT sysadm.trial.a FROM sysadm.trial and
SELECT trial.a FROM trial
Works for the same reason that SELECT t.a FROM trial t does, you are selecting alias.column. By default, Oracle uses the table name as given in the FROM clause as the alias for that table. Therefore, you can use that alias anywhere else in the query.
SELECT trial.a FROM sysadm.trial
Works because Oracle is smart enough to recognize that the owner is not neccessary, and in fact, Oracle generally ignores the owner qualification in SELECT lists viz.
SQL> SHOW USER
USER is "OPS$ORACLE"
SQL> CREATE TABLE t (id NUMBER);
Table created.
SQL> INSERT INTO t VALUES (1);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> GRANT CONNECT, RESOURCE TO u IDENTIFIED BY test;
Grant succeeded.
SQL> GRANT SELECT ON t TO u;
Grant succeeded.
SQL> CONNECT u/test;
Connected.
SQL> CREATE TABLE t (id number);
Table created.
SQL> INSERT INTO t VALUES(2);
1 row created.
SQL> COMMIT;
Commit complete.
SQL> SELECT ops$oracle.t.id, t.id
  2  FROM ops$oracle.t, t
  3  /
SELECT ops$oracle.t.id, t.id
ERROR at line 1:
ORA-00918: column ambiguously definedBut Oracle can use it when neccessary to unambiguously identify a column:
SQL> SELECT ops$oracle.t.id, u.t.id
  2  FROM ops$oracle.t, u.t;
        ID         ID
         1          2Since Oracle mostly does not care about the table owner in select lists, it is no surprise that it won't add the owner when you do:
select sysadm.trial.a from trial
HTH
John

Similar Messages

  • Advance table  column header problem

    Hi experts
    i am facing a problem in advacne table , i have created the column dynamicaly for the advance table but the column header is displaying in another column and my date field is displaying in another column ..
    i am pasting my code
    OAAdvancedTableBean tableBean = (OAAdvancedTableBean)webBean.findIndexedChildRecursive("ChargeDetailsTbl");
    OAColumnBean upadateColumn = (OAColumnBean)pageContext.getWebBeanFactory().createWebBean(pageContext,COLUMN_BEAN,null,"XXUpdate");
    OASortableHeaderBean upadateColumnHeader1 = (OASortableHeaderBean)pageContext.getWebBeanFactory().createWebBean(pageContext, SORTABLE_HEADER_BEAN, null, "XXUpdateHeader");
    upadateColumnHeader1.setPrompt("WorkPerformedDate");
    upadateColumn.setColumnHeader(upadateColumnHeader1);
    OAMessageDateFieldBean leaf1 = (OAMessageDateFieldBean)pageContext.getWebBeanFactory().createWebBean(pageContext, MESSAGE_DATE_FIELD_BEAN, null, "Leaf1");
    leaf1.setViewAttributeName("WorkPerformedDate");
    leaf1.setViewUsageName("ChargeDetailsVO");
    upadateColumn.addIndexedChild(leaf1);
    upadateColumn.setRendered(true);
    tableBean.addIndexedChild(upadateColumn);
    can any one plesae help to resolve this issue

    Hi,
    Its good to see that ur issue has been resolved. Post the solution if u can, so that somebody might get benefited. And mark the thread as anwered.
    Regards,
    Gyan

  • Function with for loop and parameter table/column names ... syntax help

    I'm trying to create a function that returns the distinct values and counts from a user defined schema/table/column.
    The code below defines an object type [stats_on_column_obj] and creates a single table of this type [stats_on_column_tab].
    The function is supposed to take three input variables: p_schema_name, p_table_name, p_column_name and return a table (above).
    I can hard code a SELECT statement into the () ... but once I try to convert it to parameters & exec immediate I am stuck. The red section is where the issue is (i think).
    Oracle 10g.
    CREATE TYPE stats_on_column_obj IS OBJECT(
      COL_VAL      VARCHAR2(500),
      COL_VAL_CNT  NUMBER    (7)
    CREATE TYPE stats_on_column_tab IS TABLE OF stats_on_column_obj;
    CREATE OR REPLACE FUNCTION get_STATS_ON_COLUMN
       p_schema_name IN varchar2,
       p_table_name IN varchar2,
       p_column_name IN  varchar2
       RETURN STATS_ON_COLUMN_tab
    IS
       l_STATS_ON_COLUMN_tab   STATS_ON_COLUMN_tab := STATS_ON_COLUMN_tab ();
       n                       INTEGER := 0;
       str_select_tbl          varchar2(5000);
    BEGIN
       str_select_tbl := 'SELECT '||p_column_name||' as col_val, count(*) as col_val_cnt FROM '||p_schema_name||'.'||p_table_name||' group by '||p_column_name;
       FOR r IN (str_select_tbl)
       LOOP
          l_STATS_ON_COLUMN_tab.EXTEND;
          n := n + 1;
          l_STATS_ON_COLUMN_tab (n) := STATS_ON_COLUMN_obj (r.col_val, r.col_val_cnt);
       END LOOP ;
       RETURN l_STATS_ON_COLUMN_tab;
    END;
    [Error] PLS-00103 (124: 4): PLS-00103: Encountered the symbol "LOOP" when expecting one of the following:   * & - + / at mod remainder rem .. <an exponent (**)> ||   multiset year DAY_
    [Error] PLS-00103 (126: 9): PLS-00103: Encountered the symbol "=" when expecting one of the following:   constant exception <an identifier>   <a double-quoted delimited-identifier> table LONG_ double ref   char time timestam
    [Error] PLS-00103 (127: 29): PLS-00103: Encountered the symbol "(" when expecting one of the following:   constant exception <an identifier>   <a double-quoted delimited-identifier> table LONG_ double ref   char time timestam
    [Error] PLS-00103 (128: 4): PLS-00103: Encountered the symbol "END" when expecting one of the following:   begin function package pragma procedure subtype type use   <an identifier> <a double-quoted delimited-identifier> form
    SELECT * FROM TABLE (get_STATS_ON_COLUMN('SCHEMAS_X','TABLE_X','COLUMN_X'));

    SCOTT@orcl > CREATE OR REPLACE
      2    FUNCTION get_STATS_ON_COLUMN(
      3                                 p_schema_name IN varchar2,
      4                                 p_table_name IN varchar2,
      5                                 p_column_name IN  varchar2
      6                                )
      7      RETURN STATS_ON_COLUMN_tab
      8      IS
      9          v_STATS_ON_COLUMN_tab STATS_ON_COLUMN_tab := STATS_ON_COLUMN_tab ();
    10          v_n                   INTEGER := 0;
    11          v_str_select_tbl      VARCHAR2(5000);
    12      BEGIN
    13          v_str_select_tbl := 'SELECT stats_on_column_obj(' || p_column_name || ',count(*)) FROM ' ||
    14                              p_schema_name || '.' || p_table_name || ' group by ' || p_column_name;
    15      EXECUTE IMMEDIATE v_str_select_tbl
    16        BULK COLLECT
    17        INTO v_STATS_ON_COLUMN_tab;
    18       RETURN v_STATS_ON_COLUMN_tab;
    19  END;
    20  /
    Function created.
    SCOTT@orcl > select  *
      2            from  table(
      3                        get_STATS_ON_COLUMN(
      4                                            'SCOTT',
      5                                            'EMP',
      6                                            'JOB'
      7                                           )
      8                       )
      9  /
    COL_VAL              COL_VAL_CNT
    CLERK                          4
    SALESMAN                       4
    PRESIDENT                      1
    MANAGER                        3
    ANALYST                        2
    SCOTT@orcl >
    Or better change it to pipelined function.
    SY.

  • Different tables' column have same value

    Hi,
    How to find out which coulmns in database are stoing a value. ex: 'Tier'
    I need to know different table's column in database have value 'Tier'.
    table1.col1 ='Tier'
    table2.col16='Tier'
    table3.col21='Tier'Thanks
    Sandy

    One possible solution is below. Take care with the performance, as the procedure is checking every schema.table.column VARCHAR ou CHAR. The number of columns can easily go to thousands and affect the overall performance of your DBMS.
    The example is explicitlly avoiding tables in schema SYS and SYSDBA.
    set serveroutput on size 999999
    declare
    cnt number;
    sql_comm varchar2(1000);
    begin
    for TRec in (select owner, table_name, column_name, data_length
                   from all_tab_columns
                  where data_type IN ('VARCHAR2', 'CHAR')
                    and owner not in ('SYS', 'SYSTEM')
                    and data_length >= 4
                  order by 1, 2, 3) loop
        sql_comm := 'select count(*) from '||TRec.owner||'.'||TRec.table_name||' where '||TRec.column_name||'= ''Tier''';
        execute immediate sql_comm into cnt;
        if cnt>0 then
            dbms_output.put_line(TRec.owner||'.'||TRec.table_name||'.'||TRec.column_name||' has '||cnt||' rows.');
        end if;   
    end loop;         
    end;
    Miguel

  • Problem with LinkToURL in a table column

    Hi,
    let's say we have a LinkToURL element with a text and an image. Then a click on the text OR a click on the image navigates to the given URL.
    This behaviour changes if you put the LinkToURL element in a table column. In that case the link is executed only if you click on the text, nothing happens if you click on the image (I assume this is a bug, of have I missed a detail?). If you have a LinkToURL element without a text and with an image only, this becomes a problem.
    One column of my table contains a single image, and a click on that image shall open a link. Is there another way to do this except using a LinkToURL element?
    Thanks,
    Karsten

    Hi Valery,
    yes, this hint is exactly what I needed. I just changed the LinkToURL to a LinkToAction, and this can be activated by clicking the text OR the image.
    The necessary coding in the action handler would then look like this:
    WDWindow wnd = wdComponentAPI.getWindowManager()
         .createExternalWindow("http://www.sap.com",
         "SAP Global", false);
    wnd.open();
    Thank you very much,
    Karsten

  • Problem when expanding Tree - Tree with nested table column

    Hi, i have created the tree using the Tree with nested table column.
    I have created a node called TREE_ROOT in the context.
    This node has few attributes which includes children_loaded, is_leaf, is_expanded.
    I have created the recursive node TREE_SUB for the above node TREE_ROOT.
    In the view, i have created the table with the master column. The above attributes have been mapped accordingly. I have created the action handler for load_children.
    In this action handler method, i receive the context_element correctly. In this method, i determine the children of the selected element and the resulting children are attached to this context_element.
    But the problem is: when i add elements to context_elements in the method load_children, these
    elements get added to the node TREE_ROOT as well.
    Please help.
    thanks and best regards,
    Pramod

    I just use some types defined in this user... Well, I hope you know what is the type definition of d_period_sec,
    don't you ? I didn't ask to provide all types existed now, only types you are
    using.
    Anyhow you have been granted with execute privilege for types you are using:
    SQL> conn tau_tll/tau_tll;
    Connected.
    SQL> create or replace type d_period_sec as object (date# date);
      2  /
    Type created.
    SQL> grant execute on d_period_sec to public with grant option;
    Grant succeeded.
    SQL> conn scott/tiger
    Connected.
    SQL> CREATE OR REPLACE TYPE unit_function AS OBJECT (
      2  xi NUMBER,
      3  yi NUMBER,
      4  xe NUMBER,
      5  ye NUMBER,
      6  xm NUMBER,
      7  ym NUMBER,
      8  v NUMBER,
      9  a NUMBER,
    10  f NUMBER,
    11  descr VARCHAR2 (20)
    12  );
    13  /
    Type created.
    SQL> grant execute on unit_function to master;
    Grant succeeded.
    SQL> CREATE OR REPLACE TYPE unit_moving_point AS OBJECT
      2  (
      3  p tau_tll.d_period_sec, -- from user TAU_TLL
      4 
      5  m unit_function
      6  )
      7  /
    Type created.
    SQL> grant execute on unit_moving_point to master;
    Grant succeeded.
    SQL> CREATE OR REPLACE TYPE moving_point_tab AS TABLE OF unit_moving_point;
      2  /
    Type created.
    SQL> grant execute on moving_point_tab to master;
    Grant succeeded.
    SQL> CREATE OR REPLACE TYPE moving_point AS OBJECT (u_tab moving_point_tab);
      2  /
    Type created.
    SQL> grant execute on moving_point to master;
    Grant succeeded.
    SQL> conn master/master
    Connected.
    SQL> CREATE TABLE MPOINTS (
      2  id NUMBER,
      3  mpoint scott.Moving_Point)
      4  NESTED TABLE mpoint.u_tab store as moving_tab;
    Table created.Rgds.

  • 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

  • OIM 9102 Schema - OSI_CHILD_OLD_VALUE column in OSI table

    Hello,
    OIM 9102 database schema has a table name called OSI which I think holds information about tasks.
    There is a column in the OSI table called “OSI_CHILD_OLD_VALUE” (Blob type). Did anyone familiar with the content of this column? What information it contains and which use case will trigger the read on the this table column?
    Thanks,

    Hello,
    I want to decrypt this particular column (OSI_CHILD_OLD_VALUE) value (type: CLOB). So, basically i need CLOB to byte [] - note that decrpt methods is overloaded.
    My program is working for type: String - it could decrypt other encrypted OIM database fields like USR_UDF_ENCRYPTED_CUSTOM_FIELD, CUSTOM FORM FIELDS, etc...
    Snippet:
    ResultSet rs = stmt.executeQuery(sql);
    while(rs.next()){
    Clob osiClob = rs.getClob("OSI_CHILD_OLD_VALUE");
    long clobLength = osiClob.length();
    // I tried with below clob data extraction methods
         <extracted_value_using> = osiClob.getAsciiStream()/osiClob.getCharacterStream()/osiClob.getSubString();
    byte[] decryptedVal = com.thortech.xl.crypto.tcCryptoUtil.decrypt(<extracted_value_using>,"DBSecretKey");
    System.out.println("Decrypted Value -->" + decryptedVal);
    Finding it pretty challenging as it is not working only for CLOB column. Any help will be appreciated.
    Thanks,

  • Problems of having a large table (columns and rows).

    hi people,
    can anyone give a list of problems that i will be facing when i have a large table(columns/rows). My table generate 5 lakhs record in a year and it keeps growing.
    if the answers is labourous, pls give the link of the web-site where i can download it.
    How to overcome it?
    Thanks in advance
    Ganapathy

    hi justin
    i understand u problem too.
    10 lakhs in Indian money = 1 million in the US.
    Iam trying to understand a system where there will be millions of record over a period of years. I felt that i need to address the problems that should be forseen before the system is developed(some thing like a priliminary investigation or feasibility study before taking up the project). So as of now i have no idea of the system, but do know that there will be millions of records. Iam trying to prepare a document that addresses these issues and how we are going to circumvent the issues and arrive at a solution.
    Thanks
    Ganapathy

  • Problem involving dynamic table columns in ECM

    Hi,
    In my current project I have got a requirement whose solution I am not able to figure out.
    My requirement is this:
    I will have a table containig budget owners name(since its compensation management in HR).There will be a table popin inside this table on the click of the personal number of the budget owner. Now the table popin will have another table with all employees name under that particular budget owner.
    The problem is that the table inside the popin will not be having fixed columns.
    Actually the columns will be coming from a function module(HRWPC_RFC_OADP_EVAL_DATAVIEW ) in the form of an internal table .
    My requirement is this how can this be handled?
    How to create the table with dynamic columns?Mind it,the data inside the table also have to binded and some of the columns will also be editable.
    Experts please help!
    Thanks and Regards,
    Saikat.

    Hello Saikat,
    I didnt understand why you want to create the table at design and change it runtime. you as well create the table at runtime. Because the table columns defined in the design time will not match number of table columns required at runtime. this depends on the outpur of your function module.
    Anyway here is the solution for your requirement
    1. create a attribute in the view controller (say MR_VIEW) of TYPE REF TO if_wd_view.
    2. in the doModifyview method write the following code
    if first_time = abap_true.
       wd_this->mr_view = view.
    endif.
    3. after calling you function module write the following code to change the biniding of the table and table columns
      data lo_table type ref to cl_wd_table.
      lo_table ?= wd_this->mr_view->get_element( id = 'TABLE'  ). "Pass the ID of the table that is created at design time
      data lo_nd_table2 type ref to if_wd_context_node.
      data lo_ndi_table2 type ref to if_wd_context_node_info.
      data lv_node_path type string.
      data lv_attribute_path type string.
      data lt_attributes type wdr_context_attr_info_map.
      data ls_attribute like line of lt_attributes.
      data lo_column type ref to cl_wd_table_column.
      data lo_text_view type ref to cl_wd_text_view.
      data lo_header type ref to cl_wd_caption.
      lo_nd_table2 = wd_context->get_child_node( 'TABLE2' ). "dynamically create context node name
      lv_node_path = lo_nd_table2->get_meta_path( abap_true ). "Get the path of this node
      lo_table->bind_data_source( path =  lv_node_path ). "change the ata
      lo_table->remove_all_columns( ). "remove all the design time columns
      lo_table->remove_all_grouped_columns( ).
      lo_ndi_table2 = lo_nd_table2->get_node_info( ).
      lt_attributes = lo_ndi_table2->get_attributes( ). "get the attributes in the context node
    "if you already have the list of attributes then you can just loop through them
      loop at lt_attributes into ls_attribute.
        concatenate lv_node_path '.' ls_attribute-name into lv_attribute_path.
        "Creating Table column
        lo_column = cl_wd_table_column=>new_table_column( view = wd_this->mr_view   ).
        "Creating table cell editor
        lo_text_view = cl_wd_text_view=>new_text_view(
              bind_text = lv_attribute_path "Path of the context attribute
              view      = wd_this->mr_view ).
        "creating header for the table column
        lo_header = cl_wd_caption=>new_caption(
            text  = ls_attribute-name
            view  = wd_this->mr_view  ).
        "Setting cell editor and header for the column
        lo_column->set_table_cell_editor( lo_text_view ).
        lo_column->set_header( lo_header ).
        "Adding the column to the table
        lo_table->add_column( the_column = lo_column  ).
      endloop.
    BR, Saravanan

  • Problem in truncate/drop partitions in a table having nested table columns.

    Hi,
    I have a table that has 2 columns of type nested table. Now in the purge process, when I try to truncate or drop a partition from this table, I get error that I can't do this (because table has nested tables). Can anybody help me telling how I will be able to truncate/drop partition from this table? IF I change column types from nested table to varray type, will it help?
    Also, is there any short method of moving existing data from a nested table column to a varray column (having same fields as nested table)?
    Thanks in advance.

    >
    I have a table that has 2 columns of type nested table. Now in the purge process, when I try to truncate or drop a partition from this table, I get error that I can't do this (because table has nested tables). Can anybody help me telling how I will be able to truncate/drop partition from this table?
    >
    Unfortunately you can't do those operations when a table has a nested table column. No truncate, no drop, no exchange partition at the partition level.
    A nested table column is stored as a separate table and acts like a 'child' table with foreign keys to the 'parent' table. It is these 'foreign keys' that prevent the truncation (just like normal foreign keys prevent truncating partions and must be disabled first) but there is no mechanism to 'disable' them.
    Just one excellent example (there are many others) of why you should NOT use object columns at all.
    >
    IF I change column types from nested table to varray type, will it help?
    >
    Yes but I STRONGLY suggest you take this opportunity to change your data model to a standard relational one and put the 'child' (nested table) data into its own table with a foreign key to the parent. You can create a view on the two tables that can make data appear as if you have a nested table type if you want.
    Assuming that you are going to ignore the above advice just create a new VARRAY type and a table with that type as a column. Remember VARRAYs are defined with a maximum size. So the number of nested table records needs to be within the capacity of the VARRAY type for the data to fit.
    >
    Also, is there any short method of moving existing data from a nested table column to a varray column (having same fields as nested table)?
    >
    Sure - just CAST the nested table to the VARRAY type. Here is code for a VARRAY type and a new table that shows how to do it.
    -- new array type
    CREATE OR REPLACE TYPE ARRAY_T AS VARRAY(10) OF VARCHAR2(64)
    -- new table using new array type - NOTE there is no nested table storage clause - arrays stored inline
    CREATE TABLE partitioned_table_array
         ( ID_ INT,
          arra_col  ARRAY_T )
         PARTITION BY RANGE (ID_)
         ( PARTITION p1 VALUES LESS THAN (40)
         , PARTITION p2 VALUES LESS THAN(80)
         , PARTITION p3 VALUES LESS THAN(100)
    -- insert the data from the original table converting the nested table data to the varray type
    INSERT INTO PARTITIONED_TABLE_ARRAY
    SELECT ID_, CAST(NESTED_COL AS ARRAY_T) FROM PARTITIONED_TABLENaturally since there is no more nested table storage you can truncate or drop partitions in the above table
    alter table partitioned_table_array truncate partition p1
    alter table partitioned_table_array drop partition p1

  • WD ABAP: Problem with Header text wrapping in Table Column

    Hi,
    I am unable to achieve Header Text wrapping for the TABLE columns. I have set the property "HeaderTextWrapping" to TRUE for each column and the "Fixed table layout" property has been set to TRUE.
    Is there some property of the table/column I have to set to achieve this? Or does selection of a specific property remove option of HeaderText Wrapping?
    Thanks,
    Adithya

    hi..
    Try increasing the width of column keeping other thing as it is as you have done. And yes check whether cell editor property wrapping is set true.

  • SQL from Table Column with Dynamic URL Problem

    This is the SQL I'm attempting to save to a table column via the Object Browser;
    select
    "a"."PBR_BRIEF_ID" "Brief ID",
    "a"."PROJECT_NUMBER" "Project",
    "b"."DESCRIPTION" "Description",
    "b"."ACTUAL_END_DATE" "Actual End",
    "b"."RFS_DATE" "RFS",
    "b"."LOCATION_CODE" "Location",
    ''||"b"."ESA_CODE"||'' "ESA",
    "b"."PROJECT_USER_STATUS" "Status",
    "b"."PROJECT_TRIGGER" "Trigger"
    from
    UPT1TRIAL.FUND_PLAN_BRIEF_LINK_CCR@NDSD "a",
    UPT1INTEGRAL.INT_PROJECT_DATA@NDSD "b"
    where
    "a"."PBR_BRIEF_ID" = :P3_BRIEF_ID and
    "a"."PROJECT_NUMBER" = "b"."PROJECT_DEFINITION_NUMBER"
    The intesting bit is the following, where a URL is return behind a particular column;
    ''||"b"."ESA_CODE"||'' "ESA",
    It's interesting because when I click on "Apply Changes" in the Object Browser, the text that appears in the column is as follows, i.e. with APP_ID and SESSION populated;
    ''||"b"."ESA_CODE"||'' "ESA",
    Why would that happen??
    The full SQL above is used in an application page with a SQL Query (PL/SQL function body returning SQL query). The basic SQL works OK but because of what the Object Browser is doing, the link does not.
    Message was edited by:
    Damian - apologies for lack of formatting!!
    Message was edited by:
    Damian

    Damian,
    Use
    & lt;
    for your &lt; tags and then the message will appear in the proper format.
    If you are using dynamic sql to generate an url with APP_ID and SESSSION you could:
    a) create page items (P1_APP_ID and P1_SESSION)
    b) compute those page items to the actual APP_ID and SESSION_ID
    c) use the value of those items while generating your dynamic sql (instead of APP_ID and SESSION)
    Then, your links will show the right APP_ID and the right SESSION.
    Denes Kubicek

  • Problem::Table Column Heading Font control

    Hi experts!
    Do we have any way to change font and its size in column heading, in Table Component.
    I tried but looks like we dont have access to table column heading. We can only enter heading but cant change its font and size.
    Thanking you in anticipation.
    Annu

    Hi!
    As workaround You can try to set size of text for table to what You want to have for headers and then set size for every <webuijsf:tableColumn> tag to what You want to have for rows.
    Thanks,
    Roman.

  • What table column size is needed to accomodate Unicode characters

    Hi guys,
    I have encounter something which i dont understand and i hope gurus here will shed some light on me.
    I am running a non-unicode database and i decided to port the data over to a unicode database.
    So
    1) i export the schema out --> data.dmp
    2) then i create the unicode database + create a user
    3) then i import the schema into the database
    during the imp i can see that character conversion will take place.
    During importing of data into the unicode database
    I encounter some error
    saying column size is too small
    so i went to check the row that has the column value that is too large to fit in the table.
    I realise it has some [][][][] data.. so i went to the live non-unicode database and find the row. Indeed it has some [][][][] rubbish data which i feel that someone has inserted other language then english into the database.
    But regardless,
    I went to modify the column size to a larger size, now the row can be accommodated. However the data is still [][][].
    q1) why so ? since now my database is unicode, during the import, this column data [][][] should be converted to unicode already but i still have problem seeing what language it is.
    q2) why at the non-unicode database, the [][][] data can fit into the table column size, but on unicode database, the same table column size need to be increase ?
    q3) while doing more research on unicode, it was said that unicode character takes up 2 byte per character. Alot of my table data are exactly the same size of the table column size.
    E.g Name VARCHAR2(5);
    value - 'Peter'
    Now if converting to unicode, characters will take 2byte instead of 1, isnt 'PETER' going to take up 10byte ( 2 byte per character ),
    why is it that i can still accomodate the data into the table column ?
    q4) now with unicode database up, i will be supporting different language characters around the world. How big should i set my column size to ? the longest a name can get ? or ?
    Thanks guys!

    /// does oracle automatically "look" at the each and individual characters in a word and determine how much byte it should take.
    Characters usually originate from a keyboard, which has an associated keyboard layout and an associated character set encoding (a.k.a code page, a.k.a. encoding). This means, the keyboard driver knows that when a key with a letter "á" on it is pressed on a French keyboard, and the associated character set encoding is MS Code Page 1252 (Oracle name WE8MSWIN1252), then one byte with the value 225 is generated. If the associated character set encoding is UTF-16LE (standard internal Windows encoding), two bytes 225 and 0 are generated. When the generated bytes travel through APIs, they may undergo character set conversions from one encoding to another encoding. The conversion algorithms use translation tables to find out how to translate given byte sequence from one encoding to another encoding. In case of translation from WE8MSWIN1252 to AL32UTF8, Oracle will know that the byte sequence resulting from conversion of the code 225 should be 195 followed by 161. For a Chinese characters, for example when converting it from ZHS16GBK, Oracle knows the resulting sequence as well, and this sequence is usually 3 bytes.
    This is how AL32UTF8 data gets into a database. Now, when Oracle processes a multibyte string, and needs to look at individual characters, for example to count them with LENGTH, or take a substring with SUBSTR, it uses information it has about the structure of the character set. Multibyte character sets are of two type: fixed-width and variable-width. Currently, Oracle supports only one fixed-width multibyte character set in the database: AL16UTF16, which is Oracle's name for Unicode UTF-16BE encoding. It supports this character set for NCHAR/NVARCHAR2/NCLOB data types only. This character set uses two bytes per each character code. To find the next code, 2 is simply added to the string pointer.
    All other Oracle multibyte character sets are variable-width character sets, including AL32UTF8. In most cases, the length of each character code can be determined by looking at its first byte. In AL32UTF8, the number of 1-bits in the most significant positions in the first byte before the first 0-bit tells how many bytes a character has. 0 such bits means 1 byte (such codes are identical to 7-bit ASCII), 2 such bits mean two bytes, 3 bits mean 3 bytes, 4 bits mean four bytes. 1 bit (e.g. the bit sequence 10) starts each second, third or fourth byte of a code.
    In other ASCII-based multibyte character sets, the number of bytes is usually determined by the value range of the first byte. Bytes below 128 means a one-byte code, bytes above 128 begin a two- or three-byte sequence, depending on the range.
    There are also EBCDIC-based (mainframe) multibyte character sets, a.k.a shift-sensitive character sets, where a sequence of two-byte codes is introduced by inserting the SO character (code 14=0x0e) and ended by inserting the SI character (code 15=0x0f). There are also character sets, like ISO-2022-JP, which use more complicated byte sequences to define the length and meaning of byte sequences but Oracle supports them only in limited number of places.
    /// e.g i have a word with 4 character. the 3rd character will be a chinese character..the rest are ascii character
    /// will oracle use 4 byte per character regardless its ascii(english) or chinese
    No.
    /// or it will use 1 byte per english character then 3 byte for the chinese character ? e.g.total - 6 bytes taken
    It will use 6 bytes.
    Thnx,
    Sergiusz

Maybe you are looking for

  • Java mapping help pls

    hi all, I've a source structure like this below in PI. <MAT> <doc type>pdf</doc type <subnumber>1234</subnumber> <id>45ABC<id> <matno>ABCD</matno> <filename>transaction1.pdf</filename> </MAT> target structure would be the same but one more field <fil

  • Canon Pixma MP460 printer doesn't function with Mavericks

    I upgraded my MacBook Pro to Mavericks over the weekend, and discovered this morning that my printer (Canon Pixma MP460) is not functioning with the new OS. I haven't been able to find software or driver updates on either the Canon or Apple sites to

  • Information about pending results recording in CO11N

    Dear Friends, We are using SAP 4.7. In this we are using 03 inspection lot for inprocess inspection. At present my user have come up with a requirement which is as mentioned below. 1) While posting qty in CO11N, if the inspeciton results for characte

  • Pacman fails to prepare the transaction

    Hi I recently am having issues upgrading my system. When I run sudo pacman -Syu I get the following: :: Starting full system upgrade... :: Replace kfilemetadata with extra/kfilemetadata4? [Y/n] y :: Replace libkscreen with extra/libkscreen4? [Y/n] y

  • Illustrator CC 2014 files saved as previous versions corrupt

    On occasion we need to save Illustrator files as version 8.0 ai files and version 3.0 eps for customers with older software and to import into industry specific software for further work (CAD). Illustrator CS6 works fine for these tasks. Using CC 201