Mapping Tool foreign keys

<field name="employee">
<extension vendor-name="kodo" key="jdbc-field-map"
value="one-one">
<extension vendor-name="kodo" key="column.ID" value="EMPLOYEE_ID"/>
</extension>
</field>
Hello all,
If I have the above field defined for one my classes in package.jdo,
should the mapping tools create the foreign keys automatically?
Thanks.

Hi Marc,
Thanks for the reply.
I tried using null and cascade for the value of the jdbc-delete-action. I
also added the property kodo.jdbc.ForeignKeyConstraints: true to
kodo.properties. In all cases the foreign key is showing up in the
schema, but not getting inserted into the database, MySQL with jdbc
driver version 3.0.15ga.
A more worrying issue to me is that fact that the joins are not showing up
in the schema. From what I understood from section 7.5.1 of the
documentation the one-one jdbc-field-map extension should add the joins.
My code still works I am just a little miffed as to why the joins are not
showing up. They do not show up for other types of jdbc-field-map, for
collections, as I would expect.
I'm pasting below the meta-data for the class in question plus the portion
of the schema.xml for that class. (If you need the full schema.xml and
meta-data please supply an email address I can send it to, as I do not
want to post this information on an open forum).
I'm also posting below the output of the mapping tool. Please tell me if
there is anything else you need.
Cheers.
<class name="TripImpJdo"
persistence-capable-superclass="trekwatch.core.security.AbstractPolicedObject"
objectid-class="TripImpJdoId">
<extension vendor-name="kodo" key="data-cache-timeout"
value="-1"/>
<extension vendor-name="kodo" key="jdbc-class-ind"
value="in-class-name">
<extension vendor-name="kodo" key="column"
value="JDOCLASS"/>
</extension>
<extension vendor-name="kodo" key="jdbc-class-map"
value="base">
<extension vendor-name="kodo" key="table"
value="tripimpjdo"/>
</extension>
<extension vendor-name="kodo" key="jdbc-field-mappings">
<extension vendor-name="kodo"
key="trekwatch.core.TWObject.authorId">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="AUTHORID"/>
</extension>
</extension>
<extension vendor-name="kodo"
key="trekwatch.core.TWObject.id">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="ID"/>
</extension>
</extension>
<extension vendor-name="kodo"
key="trekwatch.core.TWObject.timeStamp">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="TIMESTAMP0"/>
</extension>
</extension>
<extension vendor-name="kodo"
key="trekwatch.core.security.AbstractPolicedObject.copyPolicy">
<extension vendor-name="kodo" key="jdbc-field-map"
value="pc">
<extension vendor-name="kodo" key="column"
value="COPYPOLICY"/>
</extension>
</extension>
<extension vendor-name="kodo"
key="trekwatch.core.security.AbstractSecureTWObject.acl">
<extension vendor-name="kodo" key="jdbc-field-map"
value="pc">
<extension vendor-name="kodo" key="column"
value="ACL"/>
</extension>
</extension>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column"
value="JDOVERSION"/>
</extension>
<field name="activities">
<collection
element-type="trekwatch.core.activity.ActivityImpJdo"/>
<extension vendor-name="kodo" key="jdbc-field-map"
value="many-many">
<extension vendor-name="kodo" key="element-column.ID"
value="ACTIVITIES_ID"/>
<extension vendor-name="kodo" key="order-column"
value="ACTIVITIES_ORDER"/>
<extension vendor-name="kodo" key="ref-column.ID"
value="ID"/>
<extension vendor-name="kodo" key="table"
value="tripi_activities"/>
</extension>
</field>
<field name="atomSignature" persistence-modifier="persistent">
<extension vendor-name="kodo" key="jdbc-field-map"
value="pc">
<extension vendor-name="kodo" key="column"
value="ATOMSIGNATURE"/>
</extension>
</field>
<field name="budget">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="BUDGET"/>
</extension>
</field>
<field name="budgetType">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="BUDGETTYPE"/>
</extension>
</field>
<field name="description">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="DESCRIPTION"/>
</extension>
</field>
<field name="endDate">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="ENDDATE"/>
</extension>
</field>
<field name="gearList">
<extension vendor-name="kodo" key="jdbc-delete-action"
value="null"/>
<extension vendor-name="kodo" key="jdbc-field-map"
value="one-one">
<extension vendor-name="kodo" key="column.ID"
value="GEARLIST_ID"/>
</extension>
</field>
<field name="name">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="NAME0"/>
</extension>
</field>
<field name="numDays">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="NUMDAYS"/>
</extension>
</field>
<field name="startDate">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="STARTDATE"/>
</extension>
</field>
<field name="timeAvailable">
<extension vendor-name="kodo" key="jdbc-field-map"
value="value">
<extension vendor-name="kodo" key="column"
value="TIMEAVAILABLE"/>
</extension>
</field>
<field name="todoList">
<extension vendor-name="kodo" key="jdbc-field-map"
value="one-one">
<extension vendor-name="kodo" key="column.ID"
value="TODOLIST_ID"/>
</extension>
</field>
<field name="tripElements">
<collection element-type="TripElement"/>
<extension vendor-name="kodo" key="jdbc-field-map"
value="pc-collection">
<extension vendor-name="kodo" key="element-column"
value="ELEMENT"/>
<extension vendor-name="kodo" key="order-column"
value="TRIPELEMENTS_ORDER"/>
<extension vendor-name="kodo" key="ref-column.ID"
value="ID"/>
<extension vendor-name="kodo" key="table"
value="tripi_tripelements"/>
</extension>
</field>
</class>
<table name="tripimpjdo">
<pk column="ID"/>
<column name="ACL" type="varchar" size="255"/>
<column name="ATOMSIGNATURE" type="varchar" size="255"/>
<column name="AUTHORID" type="varchar" size="255"/>
<column name="BUDGET" type="integer"/>
<column name="BUDGETTYPE" type="integer"/>
<column name="COPYPOLICY" type="varchar" size="255"/>
<column name="DESCRIPTION" type="varchar" size="255"/>
<column name="ENDDATE" type="timestamp"/>
<column name="GEARLIST_ID" type="bigint"/>
<column name="ID" type="bigint" not-null="true"/>
<column name="JDOCLASS" type="varchar" size="255"/>
<column name="JDOVERSION" type="integer"/>
<column name="NAME0" type="varchar" size="255"/>
<column name="NUMDAYS" type="integer"/>
<column name="STARTDATE" type="timestamp"/>
<column name="TIMEAVAILABLE" type="integer"/>
<column name="TIMESTAMP0" type="timestamp"/>
<column name="TODOLIST_ID" type="bigint"/>
<fk delete-action="cascade" to-table="gearitemlist"
column="GEARLIST_ID"/>
<fk to-table="todolist" column="TODOLIST_ID"/>
<index name="I_TRPMPJD_GEARLIST_ID" column="GEARLIST_ID"/>
<index name="I_TRPMPJD_JDOCLASS" column="JDOCLASS"/>
<index name="I_TRPMPJD_JDOVERSION" column="JDOVERSION"/>
<index name="I_TRPMPJD_TODOLIST_ID" column="TODOLIST_ID"/>
</table>
create-schema:
[echo]
================================================================
[echo] Refreshing the schema in the data store
[echo]
================================================================
[mappingtool] 625 INFO [main] kodo.Tool - Mapping tool running on type
"class ***" with action "refresh".
[mappingtool] 1891 INFO [main] kodo.Tool - Mapping tool running on type
"class ***" with action "refresh".
[mappingtool] 1906 INFO [main] kodo.Tool - Mapping tool running on type
"class ***" with action "refresh".
(many more of the same as above for each persistent class.
[mappingtool] 2250 INFO [main] kodo.Tool - Recording mapping and schema
changes.
[mappingtool] 5063 WARN [main] kodo.jdbc.Schema - The foreign key
"F_TRPMPJD_GEARLIST" was not added to table "TRIPIMPJDO".
build:
BUILD SUCCESSFUL
Total time: 20 seconds
Marc Prud'hommeaux wrote:
Goerge-
As well as adding the jdbc-delete-action, you also want to set the
following in your kodo.properties:
kodo.jdbc.ForeignKeyConstraints: true
Also, I notice you are using MySQL: MySQL doesn't support some foreign
keys (such as deferred constraints). Is your foreign key deferred? Can
you post the schema.xml file, as well as the complete output from the
mappingtool so we can take a look at it?
In article <[email protected]>, Goerge wrote:
UPDATE again:
This dialog with myself is actually not bad.
Anyway, I've made some head way:
After reading through 16 pages of posts here, I found one with the same
problem I had, where it stated that foreign key constraints are not added
to the database unless a jdbc-delete-action extension is used.
After adding the following extension to the field in question, I still do
not get the foreign key in the database, but at least I get the following
message when running the mapping tool:
[mappingtool] 6157 WARN [main] kodo.jdbc.Schema - The foreign key
"F_TRPMPJD_GEARLIST" was not added to table "TRIPIMPJDO".
I am using MySQL with innodb tables, so foreign keys should be supported.
Is there another reason they are not being added?
Thanks again.
Marc Prud'hommeaux
SolarMetric Inc.

Similar Messages

In JDO, can a foreign key be part of a primary key?

Hi, it's possible to have a foreing key a part of a primary key in JDO?
The JDO checker is complaining about that. It says "Primary key field 'person' cannot declare relationship".
For example, if I have an entity 'Person' (id, name) and and entity 'Pet' (name, age). Can I have the primary key of 'Person' (id) as a foreign key in 'Pet', and can I have a compound primary key in 'Pet' with 'name' and 'id' as the compound key?
Thanks in advance.
Rafael

Hi Dino,
First of all, thank you very much for your answer.
I read the article, but the solution proposed isnt clear to me. The theorical solution is: You'll have to map the foreign key columns to individual simple fields in your class rather than a single related object. At runtime, you can use the values of these fields to construct an application identity instance, which you can then use to fetch the related object
I dont understand the second sentence how would I fecht the related object at runtime?
Did you try it? Could you please send me an example? I change the type of my attributes to primitive types, and I left my .jdo and .map files as if those attributes were only primary keys how would I specify the relation at runtime with the other table?
My email is [email protected], I would really appreciate your help.
Best regards,
Isidro

Foreign Keys in Primary Key Class

I am a newbie on toplink. I am getting an error when i run ejbc against the jar file with EJB2.0. One of the primary key classes two primary keys and both are foreign Keys to other tables. Primary Key class looks like this:
public class LcaCyberzoneAssocPK implements java.io.Serializable
public ValueHolderInterface lcaHolder;
public ValueHolderInterface cyberzoneDefHolder;
public LcaCyberzoneAssocPK(ValueHolderInterface lcaHolder,
ValueHolderInterface cyberzoneDefHolder)
super();
this.lcaHolder = lcaHolder;
this.cyberzoneDefHolder = cyberzoneDefHolder;
Bean Class has following four methods:
public abstract Lca getLcaHolder()
throws RemoteException;
public abstract CyberzoneDef getCyberzoneDefHolder()
throws RemoteException;
public abstract void setLcaHolder(Lca arg1)
throws RemoteException;
public abstract void setCyberzoneDefHolder(CyberzoneDef arg1)
throws RemoteException;
The error it is throwing is:
ERROR: Error from ejbc: In EJB LcaCyberzoneAssoc, lcaHolder is declared as oracle.toplink.indirection.ValueHolderInterface in the
pk class, but the corresponding getLcaHolder() method in the bean class returns com.qwest.danconfig.server.ejb.entity.Lca. These t
ypes must match.
Can you please help how to fix this or what is the correct way of doing it.
Second question is, is there any document which explains migrating toplink from EJB1.1 to EJB2.0?
Thanks

The EJB 2.0 spec does not really allow relationships in the primary key class. You may be able to get it to work by using the EJB classes, not ValueHolderInterface in primary key class.
Otherwise you will need to double map the foreign key fields as direct fields to be compliant with the spec. You can still have the one-to-one mappings but your model will need to keep both in synch and mark the one-to-one mappings as read-only.

To check the foreign keys

i need to know the table which gives a mapping of foreign keys...that is the key name its own table and then the table to which it is mapped as a foreign key

Hi 477390,
Here is the query.
col "Primary Table" forma a30
col "Primary Key constraint" forma a30
col "Child Table" forma a30
col "Reference Key constraint" forma a30
select a.table_name "Primary Table"
     ,a.constraint_name "Primary Key constraint"
     ,b.table_name "Child Table"
     ,b.constraint_name "Reference Key constraint"
from      dba_constraints a
     ,dba_constraints b
where a.constraint_name=b.r_constraint_name
and a.owner='<SCHEMA_NAME>';
Cheers,
Kamalesh JK

ADF Toplink Create Row with foreign key

Hello,
I'd like to create a new row in a table that has a required one-to-one mapping relationship (foreign key). I've created an edit form by dragging the return node of a readQuery. The columns holding foreign key values aren't added to the page(because of 1-1 relationship) and when I commit the changes errors are raised.
How do I pass the foreign key to the ADF Toplink framwork to include in the insert statement.

TopLink's persistence model is based around relationships, which represent FKs. To have these FKs properly populated you need to create the corresponding object relationships.
To do this you need to create a data action that will invoke a method on your class passing in the object you want to create the relationship with. There is currently an issue where ADF will not allow you to easily drop a set method onto an action. You will need to create a method on your bean that does not start with 'set'.
In the demos I have done I have added a method like 'populateAddress(Address)' that internally calls the set method. This populate method will show up on the data control palette and you can then drop it on the action in your page flow.
One additional tip: To access the object you want to pass in you will need to extend the default expression that reflects the current selected row in the iterator to have '.dataProvider' appended. This accesses the persistent object within row container.
If you are still struggling please contact me through the email address in my forum profile.
Doug

Foreign key Mapping based on Data - in SQL Developer Data modeler

Team
Do SQL Developer Data modeler supports Foreign Key mapping based on the Data in the Schema rather defined at the DDL ? For e.g if we implement a Objects Relation ship mapping in Data base, we don't define Foreign keys at table creation.
Toad does this feature through "AUTOMATIC FOREIGN KEYS MAPPING IN TOAD DATA MODELER" more info at (http://toadworld.com/Blogs/tabid/67/EntryId/905/Automatic-Foreign-Keys-Mapping-in-Toad-Data-Modeler.aspx)
any one know how to implement through some scripts also helps me
Regards
Raj

If you have table PKs defined and the candidate columns match those PK columns, then you can use the Discover Foreign Keys utility. Right mouse over the relational model name (node) in the left browser. It is about half way down the menu. I did a blog post about it last week on kentgraziano.com.

Mapping in OWB with primary key and foreign key relationship

Hi all,
I am new to this datawarehousing field. I have just started my career. I have to now create a mapping in owb where a table has a field which is a primary key of another table in the same staging area. If you guys could help me out with the a method it can be created that would be very helpful to me.
I thought of 2 ideas,
1. If I can use a look up, but then I am not sure if i can use a lookup for primary key, foreign key relationship. If I can use also, I do not know how to use that.
2. What if I can directly take that the first table and link the primary key of that table to the second table which uses that primary key of the first table as one of its fields.
I do not know how feasible these methods are. Please guys help me out.
Thanks in advance.

I have a similar case where table a and table b having relation but table a got inserted with data and table b is empty so there no values for foriegn key column in table b to realte with table a.
Now i want to load table b foriegn key with primary key column values of table a.
how can we do this in owb
thanks
kumar

Caching problem w/ primary-foreign key mapping

I have seen this a couple of times now. It is not consistent enough to
create a simple reproducible test case, so I will have to describe it to you
with an example and hope you can track it down. It only occurs when caching
is enabled.
Here are the classes:
class C1 { int id; C2 c2; }
class C2 { int id; C1 c1; }
Each class uses application identity using static nested Id classes: C1.Id
and C2.Id. What is unusual is that the same value is used for both
instances:
int id = nextId();
C1 c1 = new C1(id);
C2 c2 = new C2(id);
c1.c2 = c2;
c2.c1 = c1;
This all works fine using optimistic transactions with caching disabled.
Although the integer values are the same, the oids are unique because each
class defines its own unique oid class.
Here is the schema and mapping (this works with caching disabled but fails
with caching enabled):
table t1: column id integer, column revision integer, primary key (id)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Because the ids are known to be the same, the primary key values are also
used as foreign key values. Accessing C2.c1 is always non-null when caching
is disabled. With caching is enabled C2.c1 is usually non-null but sometimes
null. When it is null we get warnings about dangling references to deleted
instances with id values of 0 and other similar warnings.
The workaround is to add a redundant column with the same value. For some
reason this works around the caching problem (this is unnecessary with
caching disabled):
table t1: column id integer, column id2 integer, column revision integer,
primary key (id), unique index (id2)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id2"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id2"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Needless to say, the extra column adds a lot of overhead, including the
addition of a second unique index, for no value other than working around
the caching defect.

Tom-
The first thing that I think of whenever I see a problem like this is
that the equals() and hashCode() methods of your application identity
classes are not correct. Can you check them to ensure that they are
written in accordance to the guidelines at:
http://docs.solarmetric.com/manual.html#jdo_overview_pc_identity_application
If that doesn't help address the problem, can you post the code for your
application identity classes so we can double-check, and we will try to
determine what might be causing the problem.
In article <[email protected]>, Tom Landon wrote:
I have seen this a couple of times now. It is not consistent enough to
create a simple reproducible test case, so I will have to describe it to you
with an example and hope you can track it down. It only occurs when caching
is enabled.
Here are the classes:
class C1 { int id; C2 c2; }
class C2 { int id; C1 c1; }
Each class uses application identity using static nested Id classes: C1.Id
and C2.Id. What is unusual is that the same value is used for both
instances:
int id = nextId();
C1 c1 = new C1(id);
C2 c2 = new C2(id);
c1.c2 = c2;
c2.c1 = c1;
This all works fine using optimistic transactions with caching disabled.
Although the integer values are the same, the oids are unique because each
class defines its own unique oid class.
Here is the schema and mapping (this works with caching disabled but fails
with caching enabled):
table t1: column id integer, column revision integer, primary key (id)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Because the ids are known to be the same, the primary key values are also
used as foreign key values. Accessing C2.c1 is always non-null when caching
is disabled. With caching is enabled C2.c1 is usually non-null but sometimes
null. When it is null we get warnings about dangling references to deleted
instances with id values of 0 and other similar warnings.
The workaround is to add a redundant column with the same value. For some
reason this works around the caching problem (this is unnecessary with
caching disabled):
table t1: column id integer, column id2 integer, column revision integer,
primary key (id), unique index (id2)
table t2: column id integer, column revision integer, primary key (id)
<jdo>
<package name="test">
<class name="C1" objectid-class="C1$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t1"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c2">
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="column.id" value="id2"/>
</extension>
</field>
</class>
<class name="C2" objectid-class="C2$Id">
<extension vendor-name="kodo" key="jdbc-class-map" value="base">
<extension vendor-name="kodo" key="table" value="t2"/>
</extension>
<extension vendor-name="kodo" key="jdbc-version-ind"
value="version-number">
<extension vendor-name="kodo" key="column" value="revision"/>
</extension>
<field name="id" primary-key="true">
<extension vendor-name="kodo" key="jdbc-field-map" value="value">
<extension vendor-name="kodo" key="column" value="id"/>
</extension>
</field>
<field name="c1">
<extension vendor-name="kodo" key="dependent" value="true"/>
<extension vendor-name="kodo" key="inverse-owner" value="c2"/>
<extension vendor-name="kodo" key="jdbc-field-map" value="one-one">
<extension vendor-name="kodo" key="table" value="t1"/>
<extension vendor-name="kodo" key="ref-column.id" value="id2"/>
<extension vendor-name="kodo" key="column.id" value="id"/>
</extension>
</field>
</class>
</package>
</jdo>
Needless to say, the extra column adds a lot of overhead, including the
addition of a second unique index, for no value other than working around
the caching defect.
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Legacy Mapping Problem: Compound PK is Foreign Key

My job is to map beans using JPA onto a legacy database schema that must not get modified. I am stuck with doing the relation between two tables.
The schema is:
CREATE TABLE A (
     a1 INTEGER NOT NULL,
     a2 INTEGER NOT NULL,
     PRIMARY KEY (a1, a2)
CREATE TABLE B (
     b1 INTEGER NOT NULL,
     b2 INTEGER NOT NULL,
     b3 INTEGER NOT NULL,
     FOREIGN KEY f (b1, b2) REFERENCES A (a1, b2) ON UPDATE CASCADE ON DELETE CASCADE,
     PRIMARY KEY (b1, b2, b3)
)As you can see, both tables have compound primary keys, and the primary key of table B contains a foreign key to table A. This is typical in our DB because B in fact acts like a "inner table" (in the sense of "inner class") to A.
So far I defined both classes and provided a primary key, but the question now is, how to provide the relation between both? The relation shall be unidirectional, so that I can query all Bs belonging to one A by "myA.getBs(): Collection".
The code I have written so far is:
@Entity
public class A {
     @EmbeddedId
     private APK primaryKey;
     @OneToMany
     private Collection<B> characteristics;
@Embeddable
public class APK {
     private String a1;
     private String a2;
@Entity
public class B {
     @EmbeddedId
     private BPK primaryKey;
@Embeddable
public class BPK {
     private String b1;
     private String b2;
     private String b3;
}Unfortunately that is not working, because the JPA Provider (here: TopLink Essentials) tries to map the relationship on a third table named "A_B" that actually is not there.
So how to tell TopLink to find the mapping information in table B (just like using the foreign key f)?
Please help, I am driving nuts!

OK
So i found out the real problem
And the problem is that my CustomerHistory has a Text Field, as in a MS SQL Server TEXT Field
When i changed it to a VARCHAR, it started working
The strangest thing is that Customer also has a TEXT Field (mapped to a String) and i can do Finds without any problems
So my question now is how can i work with TEXT in CMPs ?
Thanks

Mapping error at deployment with foreign key data rule

I have created data rules for enabling foreign key constraints. There are 4 foreign key constraints on the fact table.
For the 1st foreign key ... its a single key match key1 on table 1
For the others, its a composite key .. key1 and key2 on table 2
key1 and key3 on table 3
key1 and key4 on table 4
When I implement with the single key foreign key constraint the mapping works fine. But when I apply the other foreign key data rules for composite keys, I get the following message while deploying ....
M_CNT Create Warning ORA-06550: line 209, column 3:
PL/SQL: ORA-00909: invalid number of arguments
M_CNT Create Warning ORA-06550: line 520, column 65530:
PL/SQL: SQL Statement ignored
M_CNT Create Warning ORA-06550: line 56, column 65530:
PL/SQL: SQL Statement ignored
M_CNT Create Warning ORA-06550: line 673, column 3:
PL/SQL: ORA-00909: invalid number of arguments
The data rule setup done is type Referential
Specify the number of attributes in row relationship - 2
Specify the referencing cardinality of row relationship
Minimum Count 1 Maximum Count n
Specify the referenced cardinality of row relationship
Minimum Count 1 Maximum Count n
What is it that I am doing wrong ?
Any suggestions. Help !!!!
Regards,
AW

Hi AW,
How can I overcome this situation ?The best solution as suggested by Jörg is use of surrogate keys.
For every production key (composite or single) generate a corresponding surrogate key using sequence operator in staging area.
This will not just solve your problem but it will be faster also (the joins will be faster with system-generated sequence numbers),
In a data warehouse use of production keys as primary key for linking with (foreign key) is not recommended, keep the production keys as additional attributes.
Regards,

Foreign key mapped to a unique constraint

ok here is the issue
create table parent(col1 char, col2 char);
alter table parent add constraint pk_parent primary key(col1);
alter table parent add constraint uk_parent unique(col1,col2);
insert into parent values('A','7');
*1 row created.*
create table child(col1 char, col2 char);
alter table child add constraint fk_child_parent foreign key(col1,col2) references parent(col1,col2);
insert into child values('B','4');
insert into child values('B','4')
ERROR at line 1:
ORA-02291: integrity constraint (WILDGOD.FK_CHILD_PARENT) violated - parent key
not found
thats what i expect....but
insert into child values('B',NULL);
*1 row created.*
why does it let me do this, i realize its because col2 is NULL but shouldnt it still check for col1 to be in the parent?
Please clarify, thanks in advance.

I see the same & am not sure why either.
SQL> @a
SQL> create table parent(col1 char, col2 char);
Table created.
SQL> alter table parent add constraint pk_parent primary key(col1);
Table altered.
SQL> alter table parent add constraint uk_parent unique(col1,col2);
Table altered.
SQL>
SQL> insert into parent values('A','7');
1 row created.
SQL> create table child(col1 char, col2 char);
Table created.
SQL> alter table child add constraint fk_child_parent foreign key(col1,col2) references parent(col1,col2);
Table altered.
SQL>
SQL> insert into child values('B','4');
insert into child values('B','4')
ERROR at line 1:
ORA-02291: integrity constraint (DBADMIN.FK_CHILD_PARENT) violated - parent key not found
SQL>
SQL> insert into child values('B',NULL);
1 row created.
SQL>
SQL> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

How to insert a new record to table with foreign key

I have 3 tables like this :
CREATE TABLE PERSON (
PK INTEGER NOT NULL,
NAME VARCHAR(10),
SSNUM INTEGER,
MGR INTEGER);
ALTER TABLE PERSON ADD CONSTRAINT PK_PERSON PRIMARY KEY (PK);
ALTER TABLE PERSON ADD CONSTRAINT FK_PERSON FOREIGN KEY (MGR) REFERENCES
PERSON (PK);
/* Tables
CREATE TABLE PROJECT (
PK INTEGER NOT NULL,
CODE_NAME INTEGER);
ALTER TABLE PROJECT ADD CONSTRAINT PK_PROJECT PRIMARY KEY (PK);
/* Tables
CREATE TABLE XREF (
PERSON INTEGER NOT NULL,
PROJECT INTEGER NOT NULL);
ALTER TABLE XREF ADD CONSTRAINT PK_XREF PRIMARY KEY (PERSON, PROJECT);
ALTER TABLE XREF ADD CONSTRAINT FK_XREF1 FOREIGN KEY (PERSON) REFERENCES
PERSON (PK);
ALTER TABLE XREF ADD CONSTRAINT FK_XREF2 FOREIGN KEY (PROJECT) REFERENCES
PROJECT (PK);
I do like the way of "ReverseTutoral" and the file .jdo here :
<?xml version="1.0" encoding="UTF-8"?>
<jdo>
<package name="reversetutorial">
<class name="Person" objectid-class="PersonId">
<extension vendor-name="kodo" key="class-column" value="none"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="table" value="PERSON"/>
<field name="name">
<extension vendor-name="kodo" key="data-column"
value="NAME"/>
</field>
<field name="person">
<extension vendor-name="kodo" key="pk-data-column"
value="MGR"/>
</field>
<field name="persons">
<collection element-type="Person"/>
<extension vendor-name="kodo" key="inverse"
value="person"/>
<extension vendor-name="kodo" key="inverse-owner"
value="person"/>
</field>
<field name="pk" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="PK"/>
</field>
<field name="ssnum">
<extension vendor-name="kodo" key="data-column"
value="SSNUM"/>
</field>
<field name="xrefs">
<collection element-type="Xref"/>
<extension vendor-name="kodo" key="inverse"
value="person"/>
<extension vendor-name="kodo" key="inverse-owner"
value="person"/>
</field>
</class>
<class name="Project" objectid-class="ProjectId">
<extension vendor-name="kodo" key="class-column" value="none"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="table" value="PROJECT"/>
<field name="codeName">
<extension vendor-name="kodo" key="data-column"
value="CODE_NAME"/>
</field>
<field name="pk" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="PK"/>
</field>
<field name="xrefs">
<collection element-type="Xref"/>
<extension vendor-name="kodo" key="inverse"
value="project"/>
<extension vendor-name="kodo" key="inverse-owner"
value="project"/>
</field>
</class>
<class name="Xref" objectid-class="XrefId">
<extension vendor-name="kodo" key="class-column" value="none"/>
<extension vendor-name="kodo" key="lock-column" value="none"/>
<extension vendor-name="kodo" key="table" value="XREF"/>
<field name="person">
<extension vendor-name="kodo" key="pk-data-column"
value="PERSON"/>
</field>
<field name="person2" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="PERSON"/>
</field>
<field name="project">
<extension vendor-name="kodo" key="pk-data-column"
value="PROJECT"/>
</field>
<field name="project2" primary-key="true">
<extension vendor-name="kodo" key="data-column"
value="PROJECT"/>
</field>
</class>
</package>
</jdo>
Data of those tables are :
PERSON :
| PK | NAME | SSNUM | MGR |
| 1 | ABC | 1 | 1 |
| 2 | DEF | 5 | 1 |
PROJECT
| PK | CODE_NAME |
| 1 | 12 |
| 2 | 13 |
And now I want to add a new record into table XREF : insert into XREF
values (1,1);
public void createData() {
Xref xref = new Xref();
Person person = new Person(1);
Project project = new Project(1);
xref.setPerson(person);
xref.setProject(project);
person.getXrefs().add(xref);
person.getXrefs().add(xref);
pm.currentTransaction().begin();
pm.makePersistent(xref);
pm.currentTransaction().commit();
I don't know why Kodo automatically insert new record to table PERSON ->
confilct Primary Key. The errors are :
0 [main] INFO kodo.Runtime - Starting Kodo JDO version 2.4.1
(kodojdo-2.4.1-20030126-1556) with capabilities: [Enterprise Edition
Features, Standard Edition Features, Lite Edition Features, Evaluation
License, Query Extensions, Datacache Plug-in, Statement Batching, Global
Transactions, Developer Tools, Custom Database Dictionaries, Enterprise
Databases, Custom ClassMappings, Custom ResultObjectProviders]
41 [main] WARN kodo.Runtime - WARNING: Kodo JDO Evaluation expires in 29
days. Please contact [email protected] for information on extending
your evaluation period or purchasing a license.
1627 [main] INFO kodo.MetaData -
com.solarmetric.kodo.meta.JDOMetaDataParser@e28b9: parsing source:
file:/D:/AN/Test/classes/reversetutorial/reversetutorial.jdo
3092 [main] INFO jdbc.JDBC - [ C:23387093; T:19356985; D:10268916 ] open:
jdbc:firebirdsql:localhost/3050:D:/An/test/temp.gdb (sysdba)
3325 [main] INFO jdbc.JDBC - [ C:23387093; T:19356985; D:10268916 ]
close:
com.solarmetric.datasource.PoolConnection@164dbd5[[requests=0;size=0;max=70;hits=0;created=0;redundant=0;overflow=0;new=0;leaked=0;unavailable=0]]
3335 [main] INFO jdbc.JDBC - [ C:23387093; T:19356985; D:10268916 ] close
connection
3648 [main] INFO jdbc.JDBC - Using dictionary class
"com.solarmetric.kodo.impl.jdbc.schema.dict.InterbaseDictionary" to
connect to "Firebird" (version "__WI-V6.2.972 Firebird 1.0.3)WI-V6.2.972
Firebird 1.0.3/tcp (annm)/P10") with JDBC driver "firebirdsql jca/jdbc
resource adapter" (version "0.1")
4032 [main] INFO jdbc.JDBC - [ C:25657668; T:19356985; D:10268916 ] open:
jdbc:firebirdsql:localhost/3050:D:/An/test/temp.gdb (sysdba)
4143 [main] INFO jdbc.SQL - [ C:25657668; T:19356985; D:10268916 ]
preparing statement <3098834>: INSERT INTO XREF(PERSON, PROJECT) VALUES
4224 [main] INFO jdbc.SQL - [ C:25657668; T:19356985; D:10268916 ]
executing statement <3098834>: [reused=1;params={(int)1,(int)1}]
4244 [main] INFO jdbc.SQL - [ C:25657668; T:19356985; D:10268916 ]
preparing statement <9090824>: INSERT INTO PERSON(MGR, NAME, PK, SSNUM)
VALUES (?, ?, ?, ?)
4315 [main] INFO jdbc.SQL - [ C:25657668; T:19356985; D:10268916 ]
executing statement <9090824>: [reused=1;params={null,null,(int)1,(int)0}]
4598 [main] WARN jdbc.JDBC - java.sql.SQLWarning: java.sql.SQLWarning:
resultSetType or resultSetConcurrency changed
4598 [main] WARN jdbc.JDBC - java.sql.SQLWarning: java.sql.SQLWarning:
resultSetType or resultSetConcurrency changed
4598 [main] INFO jdbc.JDBC - [ C:25657668; T:19356985; D:10268916 ] begin
rollback
4608 [main] INFO jdbc.JDBC - [ C:25657668; T:19356985; D:10268916 ] end
rollback 10ms
4628 [main] INFO jdbc.JDBC - [ C:25657668; T:19356985; D:10268916 ]
close:
com.solarmetric.datasource.PoolConnection@1878144[[requests=2;size=2;max=70;hits=0;created=2;redundant=0;overflow=0;new=2;leaked=0;unavailable=0]]
4628 [main] INFO jdbc.JDBC - [ C:25657668; T:19356985; D:10268916 ] close
connection
javax.jdo.JDOFatalDataStoreException:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
[SQL=INSERT INTO PERSON(MGR, NAME, PK, SSNUM) VALUES (null, null, 1, 0)]
[PRE=INSERT INTO PERSON(MGR, NAME, PK, SSNUM) VALUES (?, ?, ?, ?)]
GDS Exception. violation of PRIMARY or UNIQUE KEY constraint "PK_PERSON"
on table "PERSON" [code=335544665;state=null]
NestedThrowables:
com.solarmetric.kodo.impl.jdbc.sql.SQLExceptionWrapper:
[SQL=INSERT INTO PERSON(MGR, NAME, PK, SSNUM) VALUES (null, null, 1, 0)]
[PRE=INSERT INTO PERSON(MGR, NAME, PK, SSNUM) VALUES (?, ?, ?, ?)]
GDS Exception. violation of PRIMARY or UNIQUE KEY constraint "PK_PERSON"
on table "PERSON"
at
com.solarmetric.kodo.impl.jdbc.runtime.SQLExceptions.throwFatal(SQLExceptions.java:17)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:416)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:575)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:438)
at reversetutorial.Finder.createData(Finder.java:74)
at reversetutorial.Finder.main(Finder.java:141)
NestedThrowablesStackTrace:
org.firebirdsql.jdbc.FBSQLException: GDS Exception. violation of PRIMARY
or UNIQUE KEY constraint "PK_PERSON" on table "PERSON"
at
org.firebirdsql.jdbc.FBPreparedStatement.internalExecute(FBPreparedStatement.java:425)
at
org.firebirdsql.jdbc.FBPreparedStatement.executeUpdate(FBPreparedStatement.java:136)
at
com.solarmetric.datasource.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:111)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatementNonBatch(SQLExecutionManagerImpl.java:542)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatement(SQLExecutionManagerImpl.java:511
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeInternal(SQLExecutionManagerImpl.java:405)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.flush(SQLExecutionManagerImpl.java:272
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:411)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:575)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:438)
at reversetutorial.Finder.createData(Finder.java:74)
at reversetutorial.Finder.main(Finder.java:141)
at org.firebirdsql.gds.GDSException: violation of PRIMARY or UNIQUE KEY
constraint "PK_PERSON" on table "PERSON
at org.firebirdsql.jgds.GDS_Impl.readStatusVector(GDS_Impl.java:1683)
at org.firebirdsql.jgds.GDS_Impl.receiveResponse(GDS_Impl.java:1636)
at org.firebirdsql.jgds.GDS_Impl.isc_dsql_execute2(GDS_Impl.java:865)
at
org.firebirdsql.jca.FBManagedConnection.executeStatement(FBManagedConnection.java:782)
at
org.firebirdsql.jdbc.FBConnection.executeStatement(FBConnection.java:1072)
at
org.firebirdsql.jdbc.FBPreparedStatement.internalExecute(FBPreparedStatement.java:420)
at
org.firebirdsql.jdbc.FBPreparedStatement.executeUpdate(FBPreparedStatement.java:136)
at
com.solarmetric.datasource.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:111)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatementNonBatch(SQLExecutionManagerImpl.java:542)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executePreparedStatement(SQLExecutionManagerImpl.java:511)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.executeInternal(SQLExecutionManagerImpl.java:405)
at
com.solarmetric.kodo.impl.jdbc.SQLExecutionManagerImpl.flush(SQLExecutionManagerImpl.java:272)
at
com.solarmetric.kodo.impl.jdbc.runtime.JDBCStoreManager.flush(JDBCStoreManager.java:411)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.flush(PersistenceManagerImpl.java:575)
at
com.solarmetric.kodo.runtime.PersistenceManagerImpl.commit(PersistenceManagerImpl.java:438)
at reversetutorial.Finder.createData(Finder.java:74)
at reversetutorial.Finder.main(Finder.java:141)
Exception in thread "main"

First off, use the '-primaryKeyOnJoin true' flag when running the reverse
mapping tool so that you can get rid of that useless Xref class and have
a direct relation between Person and Project. See the documentation on
reverse mapping tool options here:
http://www.solarmetric.com/Software/Documentation/latest/docs/ref_guide_pc_reverse.html
But your real problem is that you are creating new objects, assigning
primary key values, and expecting them to represent existing objects.
That's not the way JDO works. If you want to set relations to existing
objects in JDO, you use the PM to look up those objects. If you try to
create new objects, JDO will assume you want to insert new records into
the DB, and you'll get PK conflicts like you see here.
There are several good books out on JDO; if you're just starting out with
it, they might save you a lot of time and help you master JDO quickly.

Problem with foreign key in entity bean in WSED..Plzzzzz help!!!!!

hi all,
m very new to ejb...m crerating container managed entity bean in wsed..The steps I have followed r as follows,
i) created 2 tables in database,one is PARENT with fields ID(Primary Key) and NAME and another is CHILD with fields ID1(Foreign Key) and NAME.
ii)created 2 entity beans... 1st is parent with fields id(key field) and name(promote getter & setter methods to local interface)...2nd is child
(choosed parent as bean super type) with fields id1 (promote getter & setter methods to local interface) and name (promote getter & setter methods to local interface)...
iii)Generated EJB to RDB mapping(choosed crreate new backend folder->meet in the middle->use existing connection->choosed the tables parent & child in the database->match by name->finish)
now m getting an error in Map.mapxmi--->"The table PARENT does not have a discriminator column"...and a warning--->"A primary key does not exist for table: CHILD in file: platform:/resource/NewFK/ejbModule/META-INF/backends/DB2UDBNT_V8_1/Map.mapxmi. Map.mapxmi NewFK/ejbModule/META-INF/backends/DB2UDBNT_V8_1 L/NewFK/ejbModule/META-INF/backends/DB2UDBNT_V8_1/Map.mapxmi"

Hi Sandra,
Many thanks for your response and providing time of yours.
Now, I have done exactly the same thing, but still it is the same.
I have created two new tables as below:
ZAAVREF (Check table)
MANDT (PK)
COUNTRY (PK) Domain:ZAACOUNT (CHAR 10)
ZAAV1 (Foreign key table)
MANDT (PK)
COUNTRY (PK) Domain:ZAACOUNT (CHAR 10)
Then I have created FK on country of foreign key table ZAAV1 and then SE16 (for table ZAAVREF)->Create Entries-> Entered values for Country only->Save....Records entered with valid Country values.
After that SE16 (for table ZAAV1)->Create Entries-->Entered an Invalid country->Save->Still the record entered to the Database successfully....
Could you please let me know where I am going wrong.
I am using SAP R/3 4.7 and creating tables using Tools->ABAP Workbench->Development->ABAP dictionary

Reverse mapping tool in 3.0.1 ignores "-schemas" option

I believe I have discovered a bug in the 3.0.1 version of the reverse
mapping tool.
Here is a script of the commands that worked fine in 3.0.0:
Script started on Mon Jan 12 11:02:19 2004
1$ which schemagen
/opt/kodo-jdo-3.0.0/bin/schemagen
2$ echo $PATH
/opt/kodo-jdo-3.0.0/bin:/sw/db/oracle/oracle817/bin:/sw/gen/sparc-sun-solaris2.9/acroread/5.06/bin:/sw/gen/sparc-sun-solaris2.9/cvs/1.11.5/bin:/sw/gen/sparc-sun-solaris2.9/esound/0.2.29/bin:/sw/gen/sparc-sun-solaris2.9/mpg123/0.59r/bin:/usr/bin:/sw/gen/sparc-sun-solaris2.9/gnupg/1.2.1/bin:/sw/gen/sparc-sun-solaris2.9/mozilla/1.3/bin:/sw/gen/sparc-sun-solaris2.9/openssh/3.7.1p2/sbin:/sw/gen/sparc-sun-solaris2.9/openssh/3.7.1p2/bin:/sw/pd/workman-1.3.4/bin:/usr/openwin/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/ccs/bin:/usr/ucb:/opt/local/bin:/sw/modules/bin:/sw/com/bin:/sw/pd/bin:/sw/pd/office52/program:/sw/pd/RealPlayer8:/users/n9208/bin:/opt/openssh/bin:/usr/dt/bin:/usr/dt/bin:/usr/openwin/bin:/sw/db/tools/bin:/sw/db/iss/bin:/usr/local/bin:/usr/local/scripts
3$ echo $CLASSPATH
:/opt/oracle/oracle9.0.1.4.zip:/opt/kodo-jdo-3.0.0:/opt/kodo-jdo-3.0.0/lib/kodo-jdo-runtime.jar:/opt/kodo-jdo-3.0.0/lib/kodo-jdo.jar:/opt/kodo-jdo-3.0.0/lib/jakarta-commons-collections-2.1.jar:/opt/kodo-jdo-3.0.0/lib/jakarta-commons-lang-1.0.1.jar:/opt/kodo-jdo-3.0.0/lib/jakarta-commons-logging-1.0.3.jar:/opt/kodo-jdo-3.0.0/lib/jakarta-commons-pool-1.0.1.jar:/opt/kodo-jdo-3.0.0/lib/jakarta-regexp-1.1.jar:/opt/kodo-jdo-3.0.0/lib/jca1.0.jar:/opt/kodo-jdo-3.0.0/lib/jdbc-hsql-1_7_0.jar:/opt/kodo-jdo-3.0.0/lib/jdbc2_0-stdext.jar:/opt/kodo-jdo-3.0.0/lib/jdo-1.0.1.jar:/opt/kodo-jdo-3.0.0/lib/jndi.jar:/opt/kodo-jdo-3.0.0/lib/jta-spec1_0_1.jar:/opt/kodo-jdo-3.0.0/lib/log4j-1.2.6.jar:/opt/kodo-jdo-3.0.0/lib/xalan.jar:/opt/kodo-jdo-3.0.0/lib/xercesImpl.jar:/opt/kodo-jdo-3.0.0/lib/xml-apis.jar:/opt/kodo-jdo-3.0.0/lib/jfreechart-0.9.13.jar:/opt/kodo-jdo-3.0.0/lib/jcommon-0.8.8.jar
4$ schemagen -p kodo.properties -f schema.xml -schemas PRODTRDTA.F0101
0 INFO [main] kodo.Tool - Schema generator running on schemas
"PRODTRDTA.F0101". This process may take some time. Enable the
kodo.jdbc.Schema logging category to see messages about the collection of
schema data.
136 INFO [main] jdbc.Schema - Reading table information for schema name
"PRODTRDTA", table name "F0101".
672 INFO [main] jdbc.Schema - Reading column information for table
"PRODTRDTA.F0101".
727 INFO [main] jdbc.Schema - Reading primary keys for schema name
"PRODTRDTA", table name "F0101".
2187 INFO [main] jdbc.Schema - Reading indexes for schema name
"PRODTRDTA", table name "F0101".
2432 INFO [main] jdbc.Schema - Reading foreign keys for schema name
"PRODTRDTA", table name "F0101".
2632 INFO [main] kodo.Tool - Writing XML schema.
5$
script done on Mon Jan 12 11:03:14 2004
Note the first line of logging output: both the schema name and table name
are properly recognized.
Here is the scripted output of the same commands in 3.0.1:
Script started on Mon Jan 12 10:29:03 2004
1$ which schemagen
/opt/kodo-jdo-3.0.1/bin/schemagen
2$ echo $PATH
/opt/kodo-jdo-3.0.1/bin:/sw/db/oracle/oracle817/bin:/sw/gen/sparc-sun-solaris2.9/acroread/5.06/bin:/sw/gen/sparc-sun-solaris2.9/cvs/1.11.5/bin:/sw/gen/sparc-sun-solaris2.9/esound/0.2.29/bin:/sw/gen/sparc-sun-solaris2.9/mpg123/0.59r/bin:/usr/bin:/sw/gen/sparc-sun-solaris2.9/gnupg/1.2.1/bin:/sw/gen/sparc-sun-solaris2.9/mozilla/1.3/bin:/sw/gen/sparc-sun-solaris2.9/openssh/3.7.1p2/sbin:/sw/gen/sparc-sun-solaris2.9/openssh/3.7.1p2/bin:/sw/pd/workman-1.3.4/bin:/usr/openwin/bin:/usr/bin:/sbin:/bin:/usr/sbin:/usr/ccs/bin:/usr/ucb:/opt/local/bin:/sw/modules/bin:/sw/com/bin:/sw/pd/bin:/sw/pd/office52/program:/sw/pd/RealPlayer8:/users/n9208/bin:/opt/openssh/bin:/usr/dt/bin:/usr/dt/bin:/usr/openwin/bin:/sw/db/tools/bin:/sw/db/iss/bin:/usr/local/bin:/usr/local/scripts
3$ echo $CLASSPATH
:/opt/oracle/oracle9.0.1.4.zip:/opt/kodo-jdo-3.0.1:/opt/kodo-jdo-3.0.1/lib/kodo-jdo-runtime.jar:/opt/kodo-jdo-3.0.1/lib/kodo-jdo.jar:/opt/kodo-jdo-3.0.1/lib/jakarta-commons-collections-2.1.jar:/opt/kodo-jdo-3.0.1/lib/jakarta-commons-lang-1.0.1.jar:/opt/kodo-jdo-3.0.1/lib/jakarta-commons-logging-1.0.3.jar:/opt/kodo-jdo-3.0.1/lib/jakarta-commons-pool-1.0.1.jar:/opt/kodo-jdo-3.0.1/lib/jakarta-regexp-1.1.jar:/opt/kodo-jdo-3.0.1/lib/jca1.0.jar:/opt/kodo-jdo-3.0.1/lib/jdbc-hsql-1_7_0.jar:/opt/kodo-jdo-3.0.1/lib/jdbc2_0-stdext.jar:/opt/kodo-jdo-3.0.1/lib/jdo-1.0.1.jar:/opt/kodo-jdo-3.0.1/lib/jndi.jar:/opt/kodo-jdo-3.0.1/lib/jta-spec1_0_1.jar:/opt/kodo-jdo-3.0.1/lib/log4j-1.2.6.jar:/opt/kodo-jdo-3.0.1/lib/xalan.jar:/opt/kodo-jdo-3.0.1/lib/xercesImpl.jar:/opt/kodo-jdo-3.0.1/lib/xml-apis.jar:/opt/kodo-jdo-3.0.1/lib/jfreechart-0.9.13.jar:/opt/kodo-jdo-3.0.1/lib/jcommon-0.8.8.jar:/opt/kodo-jdo-3.0.1/lib/jline.jar:/opt/kodo-jdo-3.0.1/lib/sqlline.jar
4$ schemagen -p kodo.properties -f schema.xml -schemas PRODTRDTA.F0101
1 INFO [main] kodo.Tool - Schema generator running on schemas "all".
This process may take some time. Enable the kodo.jdbc.Schema logging
category to see messages about the collection of schema data.
103 INFO [main] jdbc.Schema - Reading table information for schema name
"null", table name "null".
Exception in thread "main" java.lang.OutOfMemoryError
5$
script done on Mon Jan 12 11:01:45 2004
Note the first line of logging output here: the schema is listed as "all"
instead of the limited scope I had specified.
This run eventually crashes due to the fact that the account which I am
running the mapping tool in has access to thousands of tables, and thus
eventually the JVM runs out of available heap.
My workaround is to fall back to 3.0.0.

Thanks for the report. We noticed this ourselves a short while ago.
The bug will be fixed in 3.0.2.

Populating custom foreign key using EIM Import

Hi,
This is regarding a requirement wherein we are trying to populate the custom foreign key in the siebel base table using the EIM import.
The table being used are as .
S_CL_PTCL_LS ----> having vanilla PRDINT_ID foreing key to S_PROD_INT
S_CL_PTCL_LSXM--> Created custom colum x_prod_id as foreing key to S_PROD_INT
using EIM_CL_PTCL_LS ---> Created mapping for the custom foreign key field to resolve the UK cols.(NAME,BU_ID,VENDR_OU_ID)
When we are executing the EIM import PRDINT_ID column foreing key to S_PROD_INT is getting resolved properly; however the custom column x_prod_id as foreing key to S_PROD_INT in S_CL_PTCL_LSXM is not getting resolved.
The data for the resolution is same for both the mappings.
Can some let me know if it is possible to do such import for custom foreign keys/this import is only possible for the vanilla foreign key refrences.
Warm Regards,
Ashutosh

Hi,
I think the custom FK may be a mistake.
PAR_ROW_ID is the foreign key from S_CL_PTCL_LSXM to S_CL_PTCL_LS. You don’t have to create your own FK to do something that Siebel provides OOTB.
Please check that you really need the custom FK. I don't think you do. You should simply join to S_CL_PTCL_LS and then to S_PROD_INT. This is Siebel Tools 101 but I have seen this mistake many times.
Robert
Robert Ponder
Lead Architect and Director
Ponder Pro Serve
cell: 770.490.2767
fax: 770.412.8259
email: [email protected]
web: www.ponderproserve.com
Edited by: Robert Ponder on Dec 27, 2010 8:48 AM
Edited by: Robert Ponder on Dec 27, 2010 8:50 AM

Mapping Tool foreign keys

Similar Messages

Maybe you are looking for