Row/column counter for tables

Hello,
I know this is very basic, but so far examples I dug up don't really anything remotely to what I want.
I have 3 databases. Well they are defined as "connections" in SQLDeveloper I hope that's the same I am still not used to Oracle abstractions.
Each has several tables. All I want is loop through each of the 3 DBs and log row count and table count.
Say DB1:
Rows: Columns:
Table1: x y
Table2: x y
I don't really care what's inside them. I found one example that did it but it listed some system tables that aren't part of my db. Changing "owner" didn't really help.
From the value of the variable "Owner" means a database, is that correct?
Oh and I also don't care if the code is "inefficient", tables aren't that big.
Thanks in advance.
Edited by: 940349 on Jun 14, 2012 6:22 AM

not sure what you are planning to achieve, but you can use below query to get owner of table, table name , column name, number of tables by owner and number of column in a table (belonging to owner). This will require access to dba_tab_columns.
select owner,table_name,count(*) over(partition by owner) count_table,column_name,count(*) over(partition by owner,table_name) count_column from dba_tab_columns;

Similar Messages

  • How to get the selected rows & columns in the table?

    hi everybody,
                         In my application the table is kept inside the event structure.I select the cells  in the table (using mouse) on running time.How to get the selected number of rows & columns in that table?

    Hello,
    You can fill selected values of the table by writing to it or the corresponding property using a property node - the table is just a 2D array of strings.  I think for your "disable" question you are referring to the shortcut menu (when you right click).  If you are using LabVIEW 8.x, you can edit or disable that shortcut menu - just right click on your table at edit time and choose Advanced >> Run-Time Shortcut Menu.
    Best Regards,
    JLS
    Best,
    JLS
    Sixclear

  • Programatically setting column values for table

    hi...
    I am programatically setting column values for table.
    But these values are not getting reflected on table after commit.
    I mean to say,new values are not persisted after commit.
    The code is as follows,It is in Application Module class
    public void createRecord()
    OAViewObject vo = (OAViewObject)this.getOpptyLoeVO1();
    if (!vo.isPreparedForExecution())
    vo.executeQuery();
    Row row = vo.createRow();
    row.setAttribute("Id",new Number(850));
    row.setAttribute("Model","Honda");
    row.setAttribute("Role","Team Lead");
    row.setAttribute("Hours",new Number(35));
    vo.insertRow(row);
    row.setNewRowState(Row.STATUS_INITIALIZED);
    getTransaction().commit();
    Here "Id,Model,Role,Hours" are columns in table .

    Hi,
    is your VO based on an Entity Object?
    If not, you can't update values in the DB using only a View Object!
    If yes, you should control that, in your VO, you have not selected the flag "Read Only" for the EO you want to update.
    Hope this helps you.
    Bye
    Raffy

  • Row count for tables from 2 different databases

    Hi,
    i wrote a query to get counts from all the tables in one schema to another schema. this generates the select count (*) from tables and gives me the counts, but i want to get the counts such as
    table1 -- 100 -- DB1
    table1 - 110
    table2 - 230 - DB2
    table2 - 230 etc...
    here is my query that works but display of the output is the way i wanted. can someone help me getting the output as above described.
    select 'select ''PTO'', count(*) as '||(table_name)||'_count'||' from '||table_name||';'from dba_tables
    where owner = 'TEST'
    union all
    select 'select ''PFO'', count(*) as '||(table_name)||'_count'||' from '||table_name||';'from [email protected]
    where owner = 'TEST';
    thanks...

    DUPLICATE post
    count of rows in a schema tables

  • Re: Getting the current selected Row & column in adf table

    Hi,
    Our requirement is we have to retrieve both the current row and column in adf table.
    We can retrieve the current row in the backing bean like
    ViewObject view = getViewObject();
    view.getCurrentRow();
    Is it possible to retrieve selected column id or column header text as we are getting for row?
    please give some sample.
    Thanks,
    Vijay.
    Edited by: Vijayakumar Palanisamy on Jun 23, 2011 2:23 AM

    Hi John
    My exact requirement,
    1.     We have collection of records in adf table
    2.     Each cell in the row has commandImageLink (Like adding approver, edit approver, delete etc)
    Currently it’s working fine for me in the commandImageLink listener, but the problem is table is refreshed 2 time,
    while selecting a record and commandImageLink is clicked, I have to avoid 2 times refreshing,
    If it’s possible to identify a particular cell in the row selection, I can avoid the image link listener.
    we are using Jdeveloper11.1.1.4.0
    Please suggest.
    Thanks,
    Vijay

  • Select the column details for table in one column as varchar2(32000)

    Oracle Version: ORACLE 10G R 2
    Problem : Select the column details for some tables and want to store the same in VARCHAR2(32000) separated by ||
    Example:
    TABLE_NAME COLUMN_NAME DATA_TYPE
    EMP EMPNO NUMBER
    EMP ENAME VARCHAR2
    EMP JOB VARCHAR2
    EMP MGR NUMBER
    EMP HIREDATE DATE
    EMP SAL NUMBER
    EMP COMM NUMBER
    EMP DEPTNO NUMBER
    EMP RN NUMBER
    Want to store
    COLUMNS (empno||ename||job||mgr||hiredate||sal||comm||deptno||rn);

    SQL> var cur refcursor
    SQL> declare
    ctx number;
    begin
    ctx := dbms_xmlgen.newcontext('select * from emp');
    dbms_xmlgen.setNullHandling(ctx, dbms_xmlgen.empty_tag);
    open :cur for select * from xmltable('for $i in ROW return string-join($i/*, "||")' passing dbms_xmlgen.getxmltype(ctx).extract('ROWSET/ROW'));
    end;
    PL/SQL procedure successfully completed.
    SQL> print cur
    COLUMN_VALUE                                                                                       
    7369||SMITH||CLERK||7902||17.12.1980 00:00:00||800||||20                                           
    7499||ALLEN||SALESMAN||7698||20.02.1981 00:00:00||1600||300||30                                    
    7521||WARD||SALESMAN||7698||22.02.1981 00:00:00||1250||500||30                                     
    7566||JONES||MANAGER||7839||02.04.1981 00:00:00||2975||||20                                        
    7654||MARTIN||SALESMAN||7698||28.09.1981 00:00:00||1250||1400||30                                  
    7698||BLAKE||MANAGER||7839||01.05.1981 00:00:00||2850||||30                                        
    7782||CLARK||MANAGER||7839||09.06.1981 00:00:00||2450||||10                                        
    7788||SCOTT||ANALYST||7566||19.04.1987 00:00:00||3000||||20                                        
    7839||KING||PRESIDENT||||17.11.1981 00:00:00||5000||||10                                           
    7844||TURNER||SALESMAN||7698||08.09.1981 00:00:00||1500||0||30                                     
    7876||ADAMS||CLERK||7788||23.05.1987 00:00:00||1100||||20                                          
    7900||JAMES||CLERK||7698||03.12.1981 00:00:00||950||||30                                           
    7902||FORD||ANALYST||7566||03.12.1981 00:00:00||3000||||20                                         
    7934||MILLER||CLERK||7782||23.01.1982 00:00:00||1300||||10                                         
    14 rows selected.

  • Is it possible to resize the row / column of a table at run time ?

    Hello All ,
    I want to make a table where the user have to put datas . But if some data exceeds the length of the column / row the user should have the ability to resize the column / row of the table just like we are able to do at the time of designing . Is it possible ??
    Thanks .
    Bibhu .

    Hi,
    If you select a cell in the table that cannot receive data, then the expand to fit will not be available.
    However if you select an object that is in the table (like a textfield) then the option of expand to fit should be available.
    Try experimenting with the options.
    Niall

  • Why can't i change row and column height in tables?

    a mind-boggling problem to be sure. For some odd reason, I can't use the inspector to type in row/column heights for tables. I can use the up/down arrows, but those only work in increments of 1. I can manually adjust them one by one but as soon as I edit text in a different table cell, I have to start all over again. Does anyone else have this problem?

    Hi Gerry & Ric
    I had already tried both of your suggestions without any luck but I appreciate the help anyway. I should've been a bit more specific: I can actually type in the column/row height windows, but when I press return or tab, Pages ignores the numbers. I've tried using both the number pad and the regular keyboard numbers and every manner of clicking, enter, tab, control, alt......there must be some setting with my computer that is causing an incompatibility with Pages. Boh!
    Susie

  • 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

  • How to get row count(*) for each table that matches a pattern

    I have the following query that returns all tables that match a pattern (tablename_ and then 4 digits). I also want to return the row counts for these tables.
    Currently a single column is returned: tablename. I want to add the column RowCount.
    DECLARE @SQLCommand nvarchar(4000)
    DECLARE @TableName varchar(128)
    SET @TableName = 'ods_TTstat_master' --<<<<<< change this to a table name
    SET @SQLCommand = 'SELECT [name] as zhistTables FROM dbo.sysobjects WHERE name like ''%' + @TableName + '%'' and objectproperty(id,N''IsUserTable'')=1 ORDER BY name DESC'
    EXEC sp_executesql @SQLCommand

    The like operator requires a string operand.
    http://msdn.microsoft.com/en-us/library/ms179859.aspx
    Example:
    DECLARE @Like varchar(50) = '%frame%';
    SELECT * FROM Production.Product WHERE Name like @Like;
    -- (79 row(s) affected)
    For variable use, apply dynamic SQL:
    http://www.sqlusa.com/bestpractices/datetimeconversion/
    Rows count all tables:
    http://www.sqlusa.com/bestpractices2005/alltablesrowcount/
    Kalman Toth Database & OLAP Architect
    SQL Server 2014 Design & Programming
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • Trying to get row counts for all tables at a time

    Hi,
    i am trying to get row counts in database at a time with below query but i am getting error:
    its giving me ora-19202 error..please advise me
    select
          table_name,
          to_number(
            extractvalue(
              xmltype(dbms_xmlgen.getxml('select count(*) c from '||table_name))
              ,'/ROWSET/ROW/C')
              count
        from all_tables;

    ALL_TABLES returns tables/views current user has access to. These tables/views are owned not just by current user. However your code
    dbms_xmlgen.getxml('select count(*) c from '||table_name)does not specify who the owner is. You need to change it to:
    dbms_xmlgen.getxml('select count(*) c from '||owner || '.' || table_name)However, it still will not work. Why? As I said, ALL_TABLES returns tables/views current user has access to. Any type of access, not just SELECT. So if current user is, for example, granted nothing but UPDATE on some table the above select will fail. You would have to filter ALL_TABLES through ALL_SYS_PRIVS, ALL_ROLE_PRIVS, ALL_TAB_PRIVS and PUBLIC to get list of tables current user can select from. For example, code below does it for tables/views owned by current user and tables/views current user is explicitly granted SELECT:
    select
          t.owner,
          t.table_name,
          to_number(
            extractvalue(
              xmltype(dbms_xmlgen.getxml('select count(*) c from '||t.owner || '.' || t.table_name))
              ,'/ROWSET/ROW/C')
              count
        from all_tables t,user_tab_privs p
        where t.owner = p.owner
          and t.table_name = p.table_name
          and privilege = 'SELECT'
    union all
    select
          user,
          t.table_name,
          to_number(
            extractvalue(
              xmltype(dbms_xmlgen.getxml('select count(*) c from '||t.table_name))
              ,'/ROWSET/ROW/C')
              count
        from user_tables t
    OWNER                          TABLE_NAME                                                          COUNT
    SCOTT                          DEPT                                                                    4
    U1                             QAQA                                                                    0
    U1                             TBL                                                                     0
    U1                             EMP                                                                     1
    SQL> SY.

  • Get row count for different tables to the same line

    How can I get the row count for different tables in one line:
    SELECT count(A), count(B), count(C) from table tb_a A , tb_b B, tb_c C;
    Thanks!

    >
    Hi,
    How can I get the row count for different tables in one line:
    SELECT count(A), count(B), count(C) from table tb_a A , tb_b B, tb_c C;Something like this? One of the many uses for CTE's - Common Table Expressions - AKA
    subquery refactoring. Worth getting to know - very handy!
    with acount as
      select count(*) as counta from dual  -- put your table name here
    bcount as
      select count(*) as countb from dual  -- put your table name here
    ccount as
      select count(*) as countc from dual  -- put your table name here
    select a.counta, b.countb, c.countc from acount a, bcount b, ccount c;HTH,
    Paul...
    Edited by: Paulie on 25-Jul-2012 17:44

  • How do I show a count for rows that don't exist?

    Hi, I'm trying to count the number of records grouped by rank(B,C,R),month,and year. Basically, anytime a part fails testing a record is entered which records the failure Rank and occurrence date. A record is only inserted if a part failed for specific rank. So not all 3 ranks will have entries. I'm able to count all ranks by month,year that do exist. But how do I get values of 0 for the ranks that don't exist? I just created a table qa_rank that has just one column rank with 3 records(b,c,r). but its not being used as of now. rank is just a column in qa_occ record.Here is my query.
    select to_char(occdate,'YY') as yr, to_char(occdate,'MM') as mn,
    rank, count(occdate)
    from qa_occ
    where q.occdate between '1-Apr-2005'and '31-Mar-2006'
    and q.supplier = '11107'
    group by to_char(q.occdate,'YY'),to_char(q.occdate,'MM'),q.rank
    order by to_char(q.occdate,'YY'),to_char(q.occdate,'MM')
    which returns this
    YY MM RANK COUNT(OCCDATE)
    05 09 C 2
    05 10 C 2
    05 11 C 1
    05 11 R 1
    06 01 C 3
    06 02 C 1
    06 03 B 1
    06 03 C 2
    I need it to return C,B,R for everymonth. If no records exist then the count for the month,rank should be 0. Any ideas? Thanks.

    something like:
    SQL> with qa_occ as
      2  (select to_date('09/15/2005','mm/dd/yyyy') occdate, 'B3661-RYPX-A000' part, 'C' rank, 4 indexpoints from dual
      3   union all
      4   select to_date('09/25/2005','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
      5   union all
      6   select to_date('10/11/2005','mm/dd/yyyy') occdate, null part, 'C' rank, 7 indexpoints from dual
      7   union all
      8   select to_date('10/20/2005','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
      9   union all
    10   select to_date('11/11/2005','mm/dd/yyyy') occdate, null part, 'C' rank, 4 indexpoints from dual
    11   union all
    12   select to_date('11/18/2005','mm/dd/yyyy') occdate, 'B3661-RYPX-A000' part, 'R' rank, 0 indexpoints from dual
    13   union all
    14   select to_date('01/11/2006','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
    15   union all
    16   select to_date('01/25/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'C' rank, 4 indexpoints from dual
    17   union all
    18   select to_date('01/27/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'C' rank, 4 indexpoints from dual
    19   union all
    20   select to_date('02/15/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'C' rank, 4 indexpoints from dual
    21   union all
    22   select to_date('03/07/2006','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
    23   union all
    24   select to_date('03/14/2006','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
    25   union all
    26   select to_date('03/15/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'B' rank, 13 indexpoints from dual)
    27  select * from qa_occ;
    OCCDATE   PART            R INDEXPOINTS
    15-SEP-05 B3661-RYPX-A000 C           4
    25-SEP-05 B3661-RYP-A000  C           4
    11-OCT-05                 C           7
    20-OCT-05 B3661-RYP-A000  C           4
    11-NOV-05                 C           4
    18-NOV-05 B3661-RYPX-A000 R           0
    11-JAN-06 B3661-RYP-A000  C           4
    25-JAN-06 3511-RNA0-0111  C           4
    27-JAN-06 3511-RNA0-0111  C           4
    15-FEB-06 3511-RNA0-0111  C           4
    07-MAR-06 B3661-RYP-A000  C           4
    14-MAR-06 B3661-RYP-A000  C           4
    15-MAR-06 3511-RNA0-0111  B          13
    13 rows selected.
    assuming that there are only three ranks available B, C,and R we considered this as a lookup values. now in the query below we incorporate an inline view for the lookup values:
    SQL> with qa_occ as
      2  (select to_date('09/15/2005','mm/dd/yyyy') occdate, 'B3661-RYPX-A000' part, 'C' rank, 4 indexpoints from dual
      3   union all
      4   select to_date('09/25/2005','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
      5   union all
      6   select to_date('10/11/2005','mm/dd/yyyy') occdate, null part, 'C' rank, 7 indexpoints from dual
      7   union all
      8   select to_date('10/20/2005','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
      9   union all
    10   select to_date('11/11/2005','mm/dd/yyyy') occdate, null part, 'C' rank, 4 indexpoints from dual
    11   union all
    12   select to_date('11/18/2005','mm/dd/yyyy') occdate, 'B3661-RYPX-A000' part, 'R' rank, 0 indexpoints from dual
    13   union all
    14   select to_date('01/11/2006','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
    15   union all
    16   select to_date('01/25/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'C' rank, 4 indexpoints from dual
    17   union all
    18   select to_date('01/27/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'C' rank, 4 indexpoints from dual
    19   union all
    20   select to_date('02/15/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'C' rank, 4 indexpoints from dual
    21   union all
    22   select to_date('03/07/2006','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
    23   union all
    24   select to_date('03/14/2006','mm/dd/yyyy') occdate, 'B3661-RYP-A000' part, 'C' rank, 4 indexpoints from dual
    25   union all
    26   select to_date('03/15/2006','mm/dd/yyyy') occdate, '3511-RNA0-0111' part, 'B' rank, 13 indexpoints from dual)
    27  select qa.yr, qa.mn,
    28         decode(qa.rank,lk.rank,qa.rank,lk.rank) rank,
    29         sum(decode(qa.rank,lk.rank,qa.cnt,0)) cnt
    30    from (select to_char(qo.occdate,'YY') as yr,
    31                 to_char(qo.occdate,'MM') as mn,
    32                 qo.rank,
    33                 count(qo.occdate) cnt
    34            from qa_occ qo
    35          group by to_char(qo.occdate,'YY'),
    36                   to_char(qo.occdate,'MM'),
    37                   qo.rank) qa,
    38         (select 'B' rank from dual
    39          union all
    40          select 'C' rank from dual
    41          union all
    42          select 'R' rank from dual) lk
    43  group by qa.yr, qa.mn, decode(qa.rank,lk.rank,qa.rank,lk.rank)
    44  order by qa.yr, qa.mn, decode(qa.rank,lk.rank,qa.rank,lk.rank);
    YR MN R        CNT
    05 09 B          0
    05 09 C          2
    05 09 R          0
    05 10 B          0
    05 10 C          2
    05 10 R          0
    05 11 B          0
    05 11 C          1
    05 11 R          1
    06 01 B          0
    06 01 C          3
    06 01 R          0
    06 02 B          0
    06 02 C          1
    06 02 R          0
    06 03 B          1
    06 03 C          2
    06 03 R          0
    18 rows selected.
    SQL>

  • Get the Count for each row

    I'm trying to get the count for each row to total count for each month
    Something like this
    Hardware     |      Jan
    Monitors       |       5
    Processors   |      137
    Printers        |      57
    etc........
    How can I write a query for this. I can get the Hardware column but don't know how to get the next column.

    If you can provide more data like sample input DML statements it would have been wonderful..
    Assuming is , you need a pivot. Here is an article on basic Pivot..
    http://sqlsaga.com/sql-server/how-to-use-pivot-to-transform-rows-into-columns-in-sql-server/
    something like this may be..
    DECLARE @Input TABLE
    Hardware VARCHAR(20),
    [Date] VARCHAR(20)
    INSERT INTO @Input VALUES('Monitor', '01/01/2014'), ('CPU', '01/01/2014'), ('Monitor', '01/03/2014')
    , ('ABC', '01/01/2014'),('Monitor', '02/01/2014')
    ;WITH CTE AS
    SELECT Hardware, LEFT(DATENAME(M, [Date]),3) AS [MonthName] FROM @Input
    SELECT *
    FROM
    SELECT Hardware, [MonthName], COUNT(Hardware) AS Count FROM CTE GROUP BY Hardware, [MonthName]) a
    PIVOT (MAX([Count]) FOR [MonthName] IN ([Jan], [Feb])) pvt
    Please mark as answer, if this has helped you solve the issue.
    Good Luck :) .. visit www.sqlsaga.com for more t-sql code snippets and BI related how to articles.

  • How do I count the unique value pairs in two columns of a table?

    I have a table (Table 2) that is populated with data from an imported .csv file. On table 1 I need to count the unique value pairs in two columns of Table 2.
    Here's what I have:
    Date                                        Person
    7/10/2011                         A
    7/12/2011                         W
    7/12/2011                         X
    7/12/2011                         X
    7/12/2011                         X
    7/12/2011                         Z
    7/14/2011                         Z
    7/15/2011                 X
    7/16/2011                         Z
    I'm focusing on person "X" and can easily count how many days that person shows up but what I want is to see on how many unique days that person shows up.
    Here's the result I'm looking for (Person "X" shows up on 2 different days - 3 times on 7/12/2011 and once on 7/15/2011):
    X                    2
    I can't seem to find a function that allows me to do that. I also am not allowed to modify Table 2 so that leaves me to come up with a solution on Table 1.
    Any ideas would be greatly appreciated.

    Hi John,
    Not being allowed to modify Table 2 is a minor inconvenience. Just copy (using a formula) the necessary two columns onto Table 1.
    Yellow columns may be hidden. The procedure progresses from left to right. All formulas are entered into row 2 then filled down that column to the end of the table. The table must be as long as the list in column A of Table 2.
    A2: =Table 2::A
    Fill right to column B.
    Fill both columns down as far as needed.
    I've used actual Date and Time values in column A, formatted to show only the Date part, but the technique will work with text in these cells, provided all cells representing the same 'date' have exactly the same content.
    C2: =A&B
    This concatenates the contents of each row of columns A and B into a single text string.
    D2: =COUNTIF($C$2:C2,C)
    This counts the number of occurrences of the Date&Name string on the current row from the first regular cell in column C (C2) to the current cell.
    E2: =IF(COUNTIF($B$2:B2,B)=1,MAX($E$1:E1)+1,"")
    This constructs the index of first occurrences of each name, in the order they first occur. The index is used by LOOKUP in column F.
    F2: =IF(ROW()-1>MAX(E),"",LOOKUP(ROW()-1,$E,$B))
    This uses the index value created in E as a search-for value to extract a single copy of the names in column B. The result is a list of all distinct names in the list. Note that spelling differences will be counted as distinct names.The IF statement stops the listing when the last distinct name is extracted.
    G2: =IF(LEN(F)>0,COUNTIFS($B,"="&F,$D,"=1"),"")
    This counts the number of 'first occurrences of distinct Date & Name strings for each name on the list (ie. the number of distinct dates on which each name appears in the original list).
    All of the functions used are described, with at least one example for each, in the iWork formulas and Functions User Guide. You can download the guide, and the Numbers '09 User Guide, via the Help menu in numbers.
    Regards,
    Barry

Maybe you are looking for

  • Fatal bug in LAF project code

    I found a fatal error which causes the Java applet to freeze in forms 10.1.2.0.2 on both Solaris and Windows XP. I tested laf versions 1.3.3, 1.3.3.1 and 1.3.4 as well as Java versions 1.4.2 and 1.5 and 1.6. The bug is caused when you use the impleme

  • Error 824

    2015-01-29 17:10:48.72 spid54      Error: 824, Severity: 24, State: 2. 2015-01-29 17:10:48.72 spid54      SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x1557bf72; actual: 0x38e9bca4). It occurred during a r

  • Streams vs standby for HA

    We are trying to replace standby technology with Streams in 10.2 on standard edition of DB; first I think we need to upgrade to Enterprise edition, right? Next is there any goucha's there that we ned to be aware of Streams? and if it is a good idea -

  • Compressor choking on Motion render

    I've done a number of files in Motion that contain graphic elements. When I render, Compressor sometimes connects different files to the final output. Also, Compressor seems to generate a large number of timecode breaks. I think that this is happenin

  • I get this messege 5 or 6 times a day.something id trying to trick firefox into accepting an insecure update.

    messege appears 5 or 6 times a day