Data Modeler 3.0 EA1 - Logical Relation to Foreign Key not generating

When use "Engineer to Relational Model" the only time it creates foreign keys from my relations is when those relations are of the type many-to-many. I've added a Primary UID for each table and I have tried to use the Apply Naming Standard options but nothing seems to work.
I tested my design with the design rules feature I have no errors.
Does anyone have any ideas?
Greg

Hi Greg,
probably you added primary uid after first engineering to relational model. You can check whether those uids are selected in engineering dialog.
Also you can check log file in datamodeler\datamodeler\log directory for logged problems there.
Philip

Similar Messages

Data Modeler 3.0 EA1 - Logical= Attributes & Relational= Columns missing

Hi,
I imported Modeler 2.0 design into Modeler 3.0 EA1 and discovered that LOGICAL=>ATTRIBUTES and RELATIONAL=>COLUMNS options are no longer displayed.
Were these options removed from this new version or is my installation broken?
Thanks
Chiedu

Hi Chiedu,
they are removed. Your version is ok - at least for that :).
Philip

SQL Data Modeler 3.0 EA1 trying to create primary key on OT

Hi,
I'm trying to modify a primary key of an object table that was reversed (imported) from an Oracle 11.2.x RDBMS and am getting the error message "Incomplete Index definition". It is showing in the window "Index Columns Assignment". I get to the 'Primary Key Properties' window by pressing the 'Properties' button on the 'Table Properties' -> 'Primary Key'. If I try to edit the expression and then press the Ok or Apply buttons I get the error. With this be fixed in the production version? Will we be able to create a model in SQL Developer Data Modeler that generates a SQL statement similar to the following:
ALTER TABLE x_flags
ADD (CONSTRAINT x_flags_pk PRIMARY KEY (flags.id))
Thanks,
Scott K

Hi Scott,
I'm trying to modify a primary key of an object table that was reversed (imported) from an Oracle 11.2.x RDBMS and am getting the error message "Incomplete Index definition"... With this be fixed in the production version?yes
Will we be able to create a model in SQL Developer Data Modeler that generates a SQL statement similar to the following:
ALTER TABLE x_flags
ADD (CONSTRAINT x_flags_pk PRIMARY KEY (flags.id))I assume "flags" is column of object type and "id" is attribute of that type. I logged bug for that, so there will be support however not for 3.0.
Philip

Database adapter - table related by foreign key - not picking

Hi All,
we have a Invoke which picks data from database by using the query feature(not polling) of db adapter.
we are picking data from multiple tables.
there is foreign key relation between tables,which we have defined at the db adapter.
Parent - > child 1
> child 2 > child 3
> child 4 > child 5
So we have a case where parent has 3 rows but children tabls have 3000+.
This error is happening in such cases.
Please let me know.
<2009-08-06 16:58:54,833> <ERROR> <default.collaxa.cube.engine> The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information.
<2009-08-06 16:58:54,842> <WARN> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "activity manager": Failed due to unhandled bpel fault.
<2009-08-06 16:58:54,852> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> failed to handle message
ORABPEL-02182
JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "90,045". The reason is The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
     at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java:5514)
     at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5799)
     at com.collaxa.cube.engine.CubeEngine.expireActivity(CubeEngine.java:2086)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:174)
     at com.collaxa.cube.ejb.impl.ActivityManagerBean.expireActivity(ActivityManagerBean.java:145)
     at sun.reflect.GeneratedMethodAccessor76.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
     at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
     at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
     at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
     at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
     at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
     at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
     at ActivityManagerBean_LocalProxy_4bin6i8.expireActivity(Unknown Source)
     at com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessageHandler.handle(ExpirationMessageHandler.java:43)
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     at java.lang.Thread.run(Thread.java:595)
<2009-08-06 16:58:54,853> <ERROR> <default.collaxa.cube.engine.dispatch> <DispatchHelper::handleMessage> Not fatal connection error ... not retrying: class com.collaxa.cube.engine.UnhandledFaultException: Failed due to unhandled bpel fault.
<2009-08-06 16:58:54,854> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseDispatchTask::run> Failed to handle dispatch message ... exception ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "90,045". The reason is The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.instance.ExpirationMessage"; the exception is: JTA transaction is not present or the transaction is not in active state.
The current JTA transaction is not present or it is not in active state when processing activity or instance "90,045". The reason is The execution of this instance "90045" for process "XXSOA_ESP4G_ROUT_ABC_SRC" is supposed to be in a jta transaction, but the transaction is not present or in active state, please turn on the application server transaction debug logs to get more information..
Please consult your administrator regarding this error.
     at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:206)
     at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
     at java.lang.Thread.run(Thread.java:595)

Also for above issue , we increased the timeout in transaction manager
transaction-timeout and syncMaxWaitTime properties as follows:
Property     File Location     This Value Must Be...     Example
transaction-timeout     SOA_Oracle_Home\j2ee\home\config\transaction-manager.xml     Larger than the transaction-timeout value in orion-ejb-jar.xml and the syncMaxWaitTime value.     7200
transaction-timeout     SOA_Oracle_Home\j2ee\home\application-deployments\orabpel\ejb_ob_engine\orion-ejb-jar.xml     Less than the transaction-timeout value in transaction-manager.xml.
Note: You must set all transaction-timeout properties that display in this file.     3600
syncMaxWaitTime     SOA_Oracle_Home\bpel\domains\domain_name\config\domain.xml
where domain_name is the name of the domain to which you are deploying.     Less than the transaction-timeout value in orion-ejb-jar.xml.     240
2.
The above refernece was useful in resolcing our issue.
Regards
Arc

SQL Developer Data Modeler - Relation to Foreign Key Generation

SQL Developer Data Modeler 2.0.0 Build 584.
I am having trouble with Relations to Foreign Keys when Forward Engineering a Relational Model from a Logical Model.
First of all, the Naming Standard is not applied to the Foreign Keys when I perform the Engineer to Relational Model.
So I right click on the Relational Model from the Browser and Apply Naming Standards to Keys and Constraints.
I uncheck everything but Foreign Keys.
Now, Foreign Keys are named according to my Naming Standards.
However, this process also performs renames on the Column Foreign Keys even though I specifically unchecked that option.
This appears to be a BUG in the software and I haven't found a way around it.
I tried using {column} instead of {ref column} in the Naming Standard Template for Column Foreign Key, but that simply resulted in renaming my columns to "{column}".
Please confirm and/or let me know of any work-around for this.
Thanks,
Dan

Hi Philip,
Thanks for the reply.
Is this recorded as a bug to be addressed in the future?
Should I submit this problem via Oracle Support?
The other work-around I came up with is to override every Relation name in the Logical Model with the name I want to use in the Relational Model.
When the Relational Model is Engineered, this becomes my Foreign Key name.
Of course, this is not how I want to do things, so I am hoping for a bug fix someday.
Regards,
Dan

Object Types Attributes (Data Modeler 3.0 EA1.)

Hi,
Will the attribute object type support in data modeler be upgraded to the same functionality as column relational table support in 3.0? For relational columns I can attach a domain to a column, I can't attach a domain to an attribute in an object type. Also for a column I can define a 'Units', that is VARCHAR2 (30 BYTE) orVARCHAR2 (30 CHAR). If can't do this with the (Data Modeler 3.0 EA1.) for an object type's attribute. Will this be included?
Thanks,
Scott

Sue,
Thanks to you and your team for extending this to the object type (structured type) portion of SDDM 3.3 EA1 and 3.3 EA2. The object type portion of SDDM is pretty robust now for modeling and actually generating useable structures in the database (Oracle) now. With 3.3 EA2 at this point it will be much easier to take advantage of the object type features in the database and our applications. I have been waiting since Oracle version 8 for the tools team to provide a modeling tool that mirrors the functionality the server team has provided when it comes object types.
Thanks for this in SDDM 3.3 EA1 and SDDM 3.3 EA2!
ScottK

Data Modeler 3.0 EA1: Import deferrable column constraints

Importing from Data dictionary. Table has a deferrable initially deferred column constraints.
create table didmn( m number check (mod(m,2)=1) deferrable initially deferred
                  , mn number constraint didmn_modmn_chk check (mod(mn,2)=1) deferrable initially deferred
                  , constraint didmn_mnn_chk check (mn/m=3) deferrable initially deferred
                  , check (mn>m) deferrable initially deferred
                );Column level constraints are NOT DEFERRABLE in DDL Preview. Also after merge to a model they are in physical model not deferrable. As in my earlier foreign key thread Data Modeler 3.0 EA1: Import deferrable foreign key
Table level constraints are imported deferrable.
Edited by: Rafu on 19.10.2010 14:34

Hi Rafu,
EA2 is available and those DEFERRABLE problems are sorted out there.
Philip

Sql Developer Data Modeler 3.0 EA1: Engineering relationships to relational

When doing 'engineer to relational model' the relationship names are converted directly to foreign key names.
So, when the relationship between EMPLOYEE and DEPARTMENT is called 'working in' then the generated foreign key is also called 'working in' (not event 'working_in').
Is it possible to have it engineered to something like 'employee_working_in_department_fk'?
- Marc de Oliveira

Obviously, a property called "Plural" and an option for engineering using "Plural" names instead of entity names.
This would also allow us to have a nice relationship report where we could translate relationships into natural languages, like this:
Each DEPARTMENT may be employing one or more EMPLOYEES.
/ Marc

Sql Developer Data Modeler 3.0 EA1: Preference- Naming standard- Templates

I am trying to figure out how the naming standard templates work.
When I go to:
Preference -> Naming standard -> Templates
It says that 'Attribute Relation' is '{ref entity} {ref attribute}'
What is the consequence of this?
I thought, it would mean that when creating a primary key attribute (ID) on an entity (DEPARTMENT), the related "foreign key" attribute (that is automatically created in related detail entities, such as EMPLOYEES) would be named DEPARTMENT ID.
Instead it is just called ID. Is that the intended behavior?
- Marc de Oliveira
Edited by: marc66 on 2010-10-29 05:59

Marc,
you should check "FK Attribute name synchronization" setting in "Preferences>Data Modeler>Model>Logical model" - probably it's checked and you cannot change the name of FK attribute.
I found another bug here - FK attribute doesn't follow changes in referred entity - I logged it in bug database. As workaround you can apply defined templates at entity level (there is button in entity dialog) or for whole logical model (using pop-up menu in the browser).
Philip

Data Modeler - applying naming standards to relational model

Hi,
first of all thanks for the new data modeler build (584) - it really fixed some issues (e.g. unique keys with non mandatory referenced ids are now persistent) ...
BUT ... why is there an option to disable foreign key names when applying naming rule although it does not work?
I like my primary key names etc. to follow some naming rules, but I don't like foreign keys to follow rules, just because neither "Benutzer_Id3" follows the company internal naming rules nor is it very easy to understand at all.
Steps taken:
* logical model is complete
* generate relational model
* foreign key names are as intended (e.g. "User_Id_Modifier")
* right click the relational model
* click "Apply Naming Standards ..."
* remove the check mark from "Column Foreign Key"
* click "OK"
The foreign key column is changed regardless of checkbox state :-( - even deselecting all check boxes still applies naming rules to the foreign key columns.
Is there a fix/workaround for that or need I to go back to build 570?
Thanks god I still have my 570 compatible model ins SVN
regards stueckl

Hi,
unfortunately that functionality for all tables in relational model is broken - you still can use it at table level - "Naming rules" button in table dialog.
Philip

SQL Data Modeler - Problem Opening Saved Logical Model

I created a logical model in the Data Modeler tool and saved it as a .dmd file.
When I try to open the .dmd file nothing pulls up. I get the following logs:
2012-11-08 11:09:45 - Building Diagrams
2012-11-08 11:11:25 - Open Design: 'CTS'
2012-11-08 11:11:25 - Open Design: 'OK'
I created a test model and saved it as a .dmdz file and I get can it to open. I tried to revise the file type of my original model to .dmdz and when I try to open, I get the following error message and nothing shows up.
"Some objects are not loaded correctly. See the log file for details." There is nothing in the log file.
Any ideas about how to get my .dmd file to open correctly?

What worked for me was going to Tools .. Preferences .. Data Modeler, and then making sure that each of the "Default <x> Directory" specifications pointed to a part of the hard drive that my operating system login user had permission to reach. (I suggest a sub-directory under your login user's "My Documents" or "Documents" folder, or whatever your operating system calls it.) Allowing the initially blank defaults produced weird behavior on my machine. YMMV.
Mark

Sql Developer Data Modeler 3.0 EA1: Auto route off

I admire that the data modeler tries to automatically position relationships and data flows. I am sure it is very hard to automate and I don't think it works very well in this tool.
So, I am happy that you have the option of turning "auto route" off as I am quite particular about how diagrams should look.
In the EA1 it seems that even with "auto route" turned of, all connected relationships and dataflows are automatically repositioned as soon as an entity or process box is resized or moved - even the tiniest bit.
I think the tool should not reposition relationships or dataflows as long as their current position can be maintained after the connected entity/process is resized or moved. When lines have to be moved the tool should try to maintain a position as close to its original position as possible.
Let me know if there is a way to achieve this.
Also, when relationships or dataflows have to be repositioned by the tool, I think they should be placed as far away from each other as possible (giving more room for labels). Currently, it seems that the default behavior is to lump relationships and dataflows close together when they connect the same entities or processes.
/ Marc de Oliveira

it's the same in Data modeler v. 2.0No, in version 2.0 it is not the same. The line stays in place if you move the entity or process in the same direction as the line, eg a vertical line is not repositioned if you move a connected entity or process vertically. The same goes for horizontal lines.
Also, when resizing the right side or the bottom side of an entity or process, lines connected to it are not repositioned (as long as the box does not become too small).
You can get lines "more" fixed if you introduce intermediate point Intermediate point? I never heard of that. Where do I learn more about that? I could not find it in the help file.
/ Marc de Oliveira

SQL Data Modeler 3.0 EA1 (Data Modeler 3.0 EA1.)

On the newest release of Data Modeler (3.0.0 Build 649), if I have a relational table with an object type structure, I still cannot pick one of the attributes in the structure to be part of a the primary key for the relational table. Oracle 11gR2 does allow this. Will this be added/included in 3.0?
Edited by: user4179829 on Oct 11, 2010 12:25 PM

Hi Scott,
EA2 is available and the problem is fixed there.
Philip

Data Modeler 2.1 EA1 FK Constraints

Hi,
I don't know what functionality you have planed but, when I drag and drop the Master + Detail Table at the same time to the modeler window I see visually my FK Constraints. When I drag it one after the other I dont.
Most of the time I'm working on existing models. I would need the Model-Viewer to drag one table to the modeler window and have the opportunity to import all dependend tables and see all the FKs. Otherwise I wouldn't work with it but still work with JDeveloper.
Regards,
Juergen

Hi Philip,
Yes I'm talking about the viewer in 2.1 EA1
To be honest, I like the way Apex is doing it in the Object Browser / Model. You click on any table and it shows the first level dependency around it, you click on the dependend table and you get the first level dependencies of this table and so on.
So first level dependencies would be enough but I would like to have the opportunity to import a single table and tell Data Modeler import all first level dependency tables, then I want to click to a imported table and say, import all first level dependencies of this table, and so on..., just like Apex.
So first level would be a deal... :)
Juergen

Sql Developer Data Modeler 3.0 EA1: Custom transformation script

What is the object model used by:
Tools -> Design Rules -> Transformations
From looking at the examples (and guessing) I have managed to create ID attributes on all my entities, but how do I set its sequence number or set it as the primary key?
entities = model.getEntitySet().toArray();
for (var e = 0; e<entities.length; e++)
entity = entities[e];
att = entity.createAttribute();
att.setName('ID');
- Marc de Oliveira

content of XML files:
1) class described, parent class if there is one
2)<property .../>
describes property - set and get method, data type of property, default value
3) <collection ... />
describes collection of objects belonging to class - 5 collections are defined in Table.xml - columns, indexes, table check constraints, column groups and spatial definitions
- get method - to get collection
- create item method - method of described class used to create item for that collection; so for columns collection table.createColumn() will create column in table
- other methods - add, move, remove if are defined
4)other meta data
definitions in 1) .. 4) are used by Oracle SQL Developer Data Modeler, so it'll be wrong to modify those xml files
5)<roproperty ../>
Data Modeler doesn't parse/process these definitions, we decided to not filter them out however you should not rely that much on them
6)some junk left
For each object you can set your own properties and they will be persisted (also included in compare/merge in versioning) together with other information for object - look at "template table" example in transformation scripts. Here are methods you can use:
void setProperty(String key, String value);
     String getProperty(String key);
     boolean hasProperty(String key);
     boolean hasProperty(String key, String value);
     void removeProperty(String key);
     void clearProperties();
     Iterator getPropertyNames();
Philip

Data Modeler 3.0 EA1 - Logical Relation to Foreign Key not generating

Similar Messages

Maybe you are looking for