Schemas stored in BiztalkMgmt DB table

Hello,
In the Biztalk Admin Console , i can go to any schema, doubleclk and select Schema View. This shows me the actual schema.
Any idea from which BiztalkManagement DB table, the schema view is stored in?
My original thought was this would come from the gaced assembly?
please let me know
regr,
BM

Hi,
Full schema content is present in bt_XMLShare table of BizTalkMgmtDB with message type and schema ID.
Refer: BizTalkMgmtDB:
All Table Details
Rachit
Please mark as answer or vote as helpful if my reply does

Similar Messages

Authorization scheme for users stored in a database table?

Hello!
I'm trying to find out how to make an authorization scheme for database users.
I first made an authentication scheme for my current application, I named it "Authentication for database accounts", and the scheme type is "Database Accounts".
A word of explanation:_
I have a table in my database, named "USERS". Inside this table, I have the following columns:
- USERID (NUMBER)
- USERNAME (VARCHAR2(50))
- PASSWORD (VARCHAR2(50))
- EMAIL (VARCHAR2(200))
For this question, I'll take an example user. The username is USER and the password is USER. Email and UserID don't matter here, but let's just say the UserID is 1.
What I want:_
When you go to the application, and you are requested to log in (page 101), then I want a user to be able to log in with the data that has been stored in the USERS table.
So, on the login page, the user will enter USER as username, and USER as password. The authorization scheme then needs to check whether or not this username and password match the data in the USERS table. If it does, then it must sign the user in with the credentials the user entered (those being USER and USER).
I also want the UserID to be stored somewhere in the application (if possible, in an application item).
How do I do this? I've never made an authorization scheme before... I'm not too good with PL/SQL either, but I'm working on that part.
Any help is greatly appreciated.

I'm trying to find out how to make an authorization scheme for database users. I think there may be some confusion here. An authorization scheme gives the user access to different parts of an Apex Application. Database users are the users that you use to login to the database, for example with sqlplus.
From the rest of your post it sounds like you need a custom authentication scheme to validate users against a custom table. For this you need to create a custom authentication scheme and select use my custom function to authenticate. Exactly how you set up the authentication scheme depends on the version of Apex you are using. But an example of validate user function you could use is given below:
function validate_login (
p_username in varchar2
, p_password in varchar2) return boolean
is
v_result varchar2(1);
begin
select null into v_result
from USERS
where userid = p_username
and password = p_password;
return true;
when no_data_found then return false;
end validate_login;Once the user has successfully logged on the userid will be in the APP_USER apex substitution string.
And for Application Express Account Credentials, does this mean an admin must make each new user by hand?If you using Apex account credentials the user details are stored within the Apex tables. You can create users using the Apex admin application or by using the APEX_UTIL.create_user api.
Rod West

What is the best way to implement default values stored in a DB table?

[JHeadstart 10.1.3 build 78]
[JDeveloper 10.1.3 SU4]
We are struggling on how to best implement default values that are stored in a DB table. What we have is a database table with (CODE_TYPE, TABLE_NAME, COLUMN_NAME, DEFAULT_VALUE) as columns. This way the application administrator can administer default values himself/herself. Now we need to find the best way to set these table supplied default values in new rows. Globally we are aware of two ways:
- override create() method on VO
- probably create a View Object on top of the database table with default values (we are capable of transposing the table and return exactly one row with a column for each default value) and use JHeadstarts item property 'Default Value'.
We prefer the latter, since this is more declarative, however we struggle with the EL expression needed to indicate the default value.
If we have a VO named "DefaultValues" with a SELECT on a view on top of our database table (transposed) returning exactly one row, let us say:
SELECT orglanguage, orgtype, orgstatus [...]
FROM v_default_values
--> returning exactly one row
and we want an EL expression on an item that needs the value from orglanguage. What will the EL expression be? Something like:
#{data.DefaultValuesPageDef.currentrow.orglanguage.inputValue}? We tried several things but they do not work. A static default value works, but every EL expression so far does not. We know that using "data" can be dangerous, but thought JHeadstart takes care of preparing the other Page Definitions, so it might be possible when you use JHeadstart.
Or is overriding the create() method the preferred way? Or do we have to look at a Managed Bean for our default values that we refer to from EL (let us say MyAppDefaultValuesBean) and in that case: how do you associate a Managed Bean with a VO?
Any help would be appreciated. Apart from these default values, things are going rather well in this first J2EE/JHS project for us!
Toine

Steven,
Thanks for the reply. Unfortunately whatever we try, we cannot get it to work. We started looking at the second option (since we do need default values also in table lay-out new rows). We created a DefaultValues ViewObject, added it to the Application Module, added an EL expressiona to the Default Display Value property (replacing your ending ")" with a "}" offcourse ;-)), ran the JAG so that a page definition was generated for DefaultValues and we managed to get it prepared when loading for example the Organisation's jspx page. However no default value appears in a new row (not in Form, not in Table layout).
I then created a quick application on top of the HR schema, added a DefaultValues ViewObject using one calculated attribute (set Salary fixed to 1000), added the EL expression to the Salary Default Display Value property in the Employees Group, made sure the DefaultValuesPageDef is prepared by adding it to the parameter section and I see it getting prepared. I also see a managed Bean is created in the Employees-bean.xml.
In the Embedded OC4J log we see:
16:01:01 DEBUG (JhsPageLifecycle) -executing onCreate
16:01:01 DEBUG (JhsPageLifecycle) -CreateEmployeesDefaultValues bean found, applying default values to new row
2006-08-02 16:01:01.825 WARNING [ADFc] Warning: No Method onCreateEmployees and no actionBinding CreateEmployees found.
Is it this warning we should be worried about? Since no default value is created.
The managed bean (Employees-beans.xml) looks like:
<?xml version="1.0" encoding="windows-1252"?>
<!DOCTYPE faces-config PUBLIC
"-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config xmlns="http://java.sun.com/JSF/Configuration">
<managed-bean>
<managed-bean-name>CreateEmployeesDefaultValues</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.bean.DefaultValuesBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>iteratorBinding</property-name>
<value>#{bindings.EmployeesIterator}</value>
</managed-property>
<managed-property>
<property-name>defaultValues</property-name>
<map-entries>
<map-entry>
<key>Salary</key>
<value>#{data.DefaultValuesPageDef.DefaultValuesIterator.currentRow.Salary}</value>
</map-entry>
</map-entries>
</managed-property>
<managed-property>
<property-name>actionResult</property-name>
<value>CreateEmployees</value>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>searchEmployees</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.bean.JhsSearchBean</managed-bean-class>
<managed-bean-scope>session</managed-bean-scope>
<managed-property>
<property-name>bindings</property-name>
<value>#{data.EmployeesPageDef}</value>
</managed-property>
<managed-property>
<property-name>searchBinding</property-name>
<value>#{data.EmployeesPageDef.advancedSearchEmployees}</value>
</managed-property>
<managed-property>
<property-name>searchAttribute</property-name>
<value>EmployeeId</value>
</managed-property>
<managed-property>
<property-name>dataCollection</property-name>
<value>EmployeesView1</value>
</managed-property>
<managed-property>
<property-name>autoquery</property-name>
<value>true</value>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>EmployeesCollectionModel</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.bean.JhsCollectionModel</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>jhsPageLifecycle</property-name>
<value>#{jhsPageLifecycle}</value>
</managed-property>
<managed-property>
<property-name>bindings</property-name>
<value>#{bindings}</value>
</managed-property>
<managed-property>
<property-name>rangeBinding</property-name>
<value>#{bindings.EmployeesTable}</value>
</managed-property>
<managed-property>
<property-name>defaultValues</property-name>
<value>#{CreateEmployeesDefaultValues.defaultValues}</value>
</managed-property>
</managed-bean>
</faces-config>
This is the DefaultValues.xml:
<?xml version='1.0' encoding='windows-1252' ?>
<!DOCTYPE ViewObject SYSTEM "jbo_03_01.dtd">
<ViewObject
Name="DefaultValues"
BindingStyle="OracleName"
CustomQuery="true"
ComponentClass="hr.model.DefaultValuesImpl"
UseGlueCode="false" >
<DesignTime>
<Attr Name="_version" Value="10.1.3.36.73" />
<Attr Name="_codeGenFlag2" Value="Access|Coll|VarAccess" />
</DesignTime>
<ViewAttribute
Name="Salary"
IsUpdateable="false"
IsPersistent="false"
Precision="255"
Type="java.lang.String"
ColumnType="VARCHAR2"
AliasName="SALARY"
Expression="1000"
SQLType="VARCHAR" >
</ViewAttribute>
</ViewObject>
The PageDef for Defaultvalues is like:
<?xml version="1.0" encoding="UTF-8" ?>
<pageDefinition xmlns="http://xmlns.oracle.com/adfm/uimodel"
version="10.1.3.36.73" id="DefaultValuesPageDef"
Package="hr.view.pagedefs" EnableTokenValidation="false">
<parameters/>
<executables>
<iterator id="DefaultValuesIterator"
Binds="AppModuleDataControl.DefaultValues1"
DataControl="AppModuleDataControl" RangeSize="10"/>
</executables>
<bindings>
<attributeValues id="DefaultValuesSalary"
IterBinding="DefaultValuesIterator">
<AttrNames>
<Item Value="Salary"/>
</AttrNames>
</attributeValues>
<table id="DefaultValuesTable" IterBinding="DefaultValuesIterator">
<AttrNames>
<Item Value="Salary"/>
</AttrNames>
</table>
<action id="FirstDefaultValues" IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl" RequiresUpdateModel="true"
Action="12"/>
<action id="PreviousDefaultValues" IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl" RequiresUpdateModel="true"
Action="11"/>
<action id="NextDefaultValues" IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl" RequiresUpdateModel="true"
Action="10"/>
<action id="LastDefaultValues" IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl" RequiresUpdateModel="true"
Action="13"/>
<methodAction RequiresUpdateModel="true" Action="999"
id="advancedSearchDefaultValues"
IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl"
InstanceName="AppModuleDataControl.dataProvider"
MethodName="advancedSearch"
ReturnName="AppModuleDataControl.methodResults.AppModuleDataControl_dataProvider_advancedSearch_result"
IsViewObjectMethod="false">
<NamedData NDName="viewObjectUsage"
NDValue="#{searchDefaultValues.dataCollection}"
NDType="java.lang.String"/>
<NamedData NDName="arguments" NDValue="#{searchDefaultValues.arguments}"
NDType="java.util.ArrayList"/>
<NamedData NDName="allConditionsMet"
NDValue="#{searchDefaultValues.allConditionsMet}"
NDType="java.lang.Boolean"/>
</methodAction>
<action id="setCurrentRowWithKeyDefaultValues"
IterBinding="DefaultValuesIterator"
InstanceName="AppModuleDataControl.DefaultValues1"
DataControl="AppModuleDataControl" RequiresUpdateModel="false"
Action="96">
<NamedData NDName="rowKeyStr" NDValue="#{row.rowKeyStr}"
NDType="java.lang.String"/>
</action>
<action id="CreateDefaultValues" IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl" RequiresUpdateModel="true"
Action="40"/>
<action id="DeleteDefaultValues" IterBinding="DefaultValuesIterator"
DataControl="AppModuleDataControl" RequiresUpdateModel="false"
Action="30"/>
<action id="Commit" RequiresUpdateModel="true" Action="100"
DataControl="AppModuleDataControl"/>
<action id="Rollback" RequiresUpdateModel="false" Action="101"
DataControl="AppModuleDataControl"/>
</bindings>
</pageDefinition>
We do not understand what is wrong and why the default values do not get created in the new rows (and it is taking us far too much time). Any chance the EL expression is still wrong? It is a shame that any syntax errors in EL expressions are not visible in some logfile. It looks like when EL expressions are wrong, they are ignored instead of raising an error...
Toine

Stored procedure accessing system table

I am using a stored procedure to access tables in other schemas. I pass the schema and table name as parameters to the stored procedure. I use these two variables to create a cursor of column names from all_tab_columns table. When I access all_tab_columns from SQL Plus, the right result is returned. When the procedure executes the same select statement in the same schema and using the same search criteria, the table I am looking for can not be found.
Example:
select count(column_name) from all_tab_columns where owner = 'MYADM' and table_name = 'MYTABLE';
This will return the correct number of columns when executed in SQL Plus.
cursor mycursor is
select count(column_name) from all_tab_columns where owner = p_owner and table_name = p_table;
This cursor, when used in my stored procedure, finds nothing when p_owner is set to MYADM and p_table is set to MYTABLE.
I've tried granting all permissions to the calling schema with no positive results. I am aware that the calling schema is not required to have the necessary privileges when a procedure accesses data in other schemas. So I don't understand what the problem is. I greatly appreciate anyone's help.
Cyrus

Hi,
try this, probaly this'll give you the desired output :
Procedure Column_cnt
( p_owner IN varchar2,
p_table IN varchar2 ) IS
cursor c1 is
select count(column_name) col_cnt from all_tab_columns where owner = upper(p_owner)
and table_name = upper(p_table);
BEGIN
for i in c1 loop
dbms_output.put_line(i.col_cnt);
end loop;
END;
Now from SQLPLUS type :
exec column_cnt('OWNER','TABLE_NAME')
Note: parameters are in Varchar2, so they should be within quotes.
But do you really want a cursor to store a single row, single column value, cursors are for fetching multiple rows/columns that means for a result set.
if you want to get only count(column_name) then you could re-write the procedure like this way :
Procedure Column_cnt
( p_owner IN varchar2,
p_table IN varchar2 ) IS
col_cnt number;
BEGIN
select count(column_name) into col_cnt from all_tab_columns where owner = upper(p_owner)and table_name = upper(p_table);
dbms_output.put_line(i.col_cnt);
END;
Thanks
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by cyrus eslami ([email protected]):
I am compiling and invoking the procedure in a schema that has the correct privileges granted to it.
-Cyrus<HR></BLOCKQUOTE>
null

The size of a XML document stored in a XMLType table

Is there a way to find out (via SQL) the size of a XML document stored in a XMLType table or XMLType column (storage OR based)?
For instance in the way you could it retrieve if the XML document was stored in an XMLType column (CLOB based)
SQL> r
1 select dbms_lob.getlength(t.gegevens.getclobval()) "SIZE"
2 from hgo.hgo010_detam t
3* where rownum < 2
SIZE
2750

Is there a way to find out (via SQL) the size of a XML document stored in a XMLType table or XMLType column (storage OR based)?
For instance in the way you could it retrieve if the XML document was stored in an XMLType column (CLOB based)
SQL> r
1 select dbms_lob.getlength(t.gegevens.getclobval()) "SIZE"
2 from hgo.hgo010_detam t
3* where rownum < 2
SIZE
2750

Workflow attchment data stored in which SAP Tables

Hi,
In Leave workflow when approver rejects it the approver(Agent) provide the reason for rejection as an attachment.
I have to send the external mail to the employee.
I am able to send the mail with fixed information, however unable to extract the information from attachment ( want to know in which SAP Tables say SW* this information is stored) or any other solution.
Help Please.
Praveen Jain

You really shouldn't worry about that. Use the access functions instead.
If you are thinking about the e-mail address for a user, use the function module BAPI_USER_GET_DETAIL.
If you are thinking about the e-mail address for an employee (which is not stored in the same table), one solution is to use BAPI_EMPLCOMM_GETLIST and look for an entry with subtype 10 (this one is SAP standard I believe) or any custom subtype which should hold e-mail address.

Tables report are stored in which db table

tables report are stored in which db table ?and can we do remote comparision between this in dev and prd

Hi,
Goto your report.
Display the source code.
Goto Utilities-----> versions--
> versions management
Click on remote comparision button.
On the pop-up which appears subsequently, enter the sys name with which u want to compare ur code.
<b>Reward if helpful</b>
Regards.
Pritha.

Maximun no of data stored in a internal table

Hello experts,
I need two things,
Maximum no of data can be stored to an internal table, as per my knowledge it probably max 2 GB, and the number of records
depends on the table line type also.
Can anyone give any tentaive maximum no ?
again i need to store them in application server,what is the maximum no of records which can be downloaded to application server.
I guess in both cases (max data append to internal table and stored in application server) 50 lakhs 5 million should work.
Actually we will have to run the job anf it will contain huge data, so we can noy just check by changing no of limit.
It will be helpful for us if it can be exceeded more than 50 lakhs 5 million also.
If anyone can give some idea, it will really help us a lot.
Edited by: Thomas Zloch on Mar 7, 2012

You can get a good overview over the available memory in transaction RZ10, choose your instance profile, then "basic maintenance" and "memory management". Read the F1 help of the various parameters and consult your system administrator, as already suggested, also regarding available disk space on the application server, which should be much more, on average.
If you deal with large volumes of data, use block processing for filling your internal tables and writing to the app server, clear all tables before processing the next block, then you should stay well below your memory limits.
Thomas

Displaying html stored in a database table in a region

Hi All,
I would like to pass html to regions on the page which is stored in a database table.
I have got this working for simple html (call a packaged function to get the html and then in a PL/SQL Anonymous Block htp.p(f_get_html(:P1_param1,'REGION1')); to display it within the region ) but what I would also like to take the html generated for charts/graphs etc out of the application and also put them into the database table so that the position on the page can be determined by database tables.(i.e. have a page with lots of regions and assign html to them at runtime). I am struggling with substituting all the necessary parameters into the HTML returned from the database and how it should be formatted.
Any help appreciated and if I get any further I will update the post

I have actually managed to achive this now. When I get chance I will post the code.
The idea is that a page could have say 6 regions and depending on choices made (i.e. selected project or the individual user permissions) there are regions which you would want to display and regions you dont. Also, you may want to move regions around the page so that the important ones for that user or project etc. are at the top.
You can then, on entering a page, query database tables to decide what is to be displayed in region1, region 2 etc. and then getting the html from the database for that region and displaying it.
I have successfully done this now with embedded Oracle Reports showing graphs which look better than the SVG graphs and are more flexible.

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

Stored procedures for User Tables

Can somebody please help me with this matter?. I need to add stored procedures for user tables. Is there any way of doing so?.
Thanks in advance.
Ernesto.

Ernesto,
You have posted multiple threads for the same question. Please check the other thread and close this one:
Stored procedures in User Tables
Thanks,
Gordon

Where is schema stored?

Hi,
I know that "Berkeley DB XML" can validate a xml documents againts a schema.
My question is :
Where the schema is stored?
Can it be stored in a container?
Regards,
Cezary

Cezary,
Documents need to reference their schema, and if that reference
is to the file system or over the network, and BDB XML is
configured to access external data, it will be resolved.
Since schema are XML they can be stored in a container, but are
not treated specially by the system. In order to reference a schema
stored inside a container, you'd need to implement and XmlResolver
instance that knows how to resolve the schema when referenced.
Using that interface, it would not be difficult for an application to create
its own schema repository in one or more BDB XML containers.
Regards,
George

How do I change the partition scheme to use GUID partition Table.

How do I change the partition scheme to use GUID partition Table so I can get Snow Leopard to download on my 10.5 disk.
When I insert the disk it asks me to select the disk where you want to install MAC OS X.It only give me one option the 10.5.
when I click on it it says...
"10.5" can't be used because it doesn't use the GUID Partition Table scheme.
Use Disk Utility to change the partition scheme. Select the disk, choose the Partition tab, select the Volume Scheme and then click Options.
I tried to do what it says and I can not find what it is saying. This is the info about my MacBook.
Model Name: MacBook
Model Identifier: MacBook4,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.4 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MB41.00C1.B00
SMC Version (system): 1.31f0
Thank you for your help!

The GUID partition option is one of three possible choices (click the "Options" button in the Partition") menu - be careful to have a full backup as changing the partition scheme will force an erasure on the disk. Take a look at this Apple support article for more complete information:
Firmware updates for Intel-based Macs require a GUID partition scheme - Apple Support
Ignore the stuff about firmware updates and just look at the changing GUID partition scheme.
Good luck - and don't forget about the full backup BEFORE making this sort of change.

Stored procedure for creating tables

Is it possible to create a stored procedure which only contains create tables? I prepare everything on an environment and want to transfer everything, except the data, on anothe environment. Therfore I thought of an stored procedure which does everything automatically. Additional I want to create a package which contains all necessary stored procedures (which are already finished). Is it better to insert the create-table-lines in the package?
Thanks for your help!

PL/SQL is not the appropriate tool for this.
What does Oracle RDBMS products like Apex use to install? SQL*Plus scripts. A combination of SQL code and anonymous PL/SQL blocks.
This is also what we use to install any one of a dozen Oracle systems we have developed.. it is as simple as running 'sqlplus "/ as sysdba" @installer <tablespace> <schema> <password>'.
Trying to do this type of thing in PL/SQL... lots of disadvantages, lots of complexities, and very little (if any) benefit.

Additional receipts Information stored in which database table

Hi All,
I Know addtional receipts can be controled VIA table V_T706B1_B.
But when we have to activae the link under Travel Expense Manager ->Trip receipts ->Additio Receipts Information -> Additional Receipts Information via transaction FITVFELD.
I want to know , If I make change to this field what is the background table the changes will be stored.
Thanks in advance,

Hello,
One thing is that if someone is customizing in ESS then the transaction is FITVFELD_WEB.
The whole tab related customization are stored in the table T706S.
When you open the transaction FITVFELD_WEB or FITVFELD then it opens the trip schema.
Double click on the trip schema. Then you will see the many check box and fields to be filled.
Press F1 on that field and you will get the table name for the text.
If you want to check who made this changes then go to SE03 transaction and in object type write 'TABU' and then in front of that in the text field write the table name for which you want to check.
you will get all the users who have made the changes in that table entries. you can then catch him.

Schemas stored in BiztalkMgmt DB table

Similar Messages

Maybe you are looking for