Data Modeler version 2.0.0 - Export to reporting schema error

Hi i have the Oracle SQL Developer Data Modeler version 2.0.0 installed.
When i try to export one diagram to the reporting schema, i get the following error : "Error occurred while exporting to Reporting Schema.See the log file for details".
The log file has no errors.
The repository owner is DBA.
The connection is ok.
Can you help me?
Thanks in advance
Paolo.

Sorry for the log. I looked at the one at the bottom of the window, i didn't know of the one in the directory.
I purged the log and i tried again with an account with only connect,resource privileges.
At the bottom of the message you'll find the log.
The java.exe points refers to the one in the java directory of the data modeler (i downloaded the one with Java included).
Thanks for the answer
Paolo.
SQL> create user p identified by p default tablespace f2 temporary tablespace temp;
User created
SQL> grant connect,resource to p;
Grant succeeded
2009-10-23 09:53:10,921 [main] INFO ApplicationView - Oracle SQL Developer Data Modeler Version: 2.0.0 Build: 570
2009-10-23 09:53:11,546 [main] WARN AbstractXMLReader - There is no file with default domains (path: domains name: defaultdomains)
2009-10-23 09:56:36,984 [Thread-4] ERROR ReportsHandler - Error Exporting to Reporting Schema:
java.sql.SQLException: Missing IN or OUT parameter at index:: 10
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:110)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:171)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
     at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OraclePreparedStatement.java:1737)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3376)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3462)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1061)
     at oracle.dbtools.crest.exports.reports.RSCheckConstraint.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSColumns.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSRelationalModel.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)

Similar Messages

Sql Developer Data Modeler 3.0 EA1: Export - To reporting schema

When launching Export -> To reporting schema the schema tables are created and messages show that data is being generated but after indicating that it "Exporting Diagrams" I get the following error message:
"Error occurred while exporting to Reporting Schema. See the log file for details."
and all the tables are left empty.
The message log is not indicating that anything went wrong.
What could be the problem?
- Marc

This is probably what you are looking for:
2010-10-14 14:56:43,680 [Thread-11] ERROR ReportsHandler - Error Exporting to Reporting Schema:
java.lang.NullPointerException
     at oracle.dbtools.crest.model.design.DesignPart.doSetMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.model.design.DesignPart.setMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.model.design.DesignPart.setMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSDiagrams.ensureMainViewVisible(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSDiagrams.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
What does it mean?
/ Marc de Oliveira

Export to Reporting Schema failure

Can I get some help with the below error when attempting to export to reporting schema. I've reviewed the repository and 79 tables were created, but no data. I looks like this error occurs at the end of the process, but prior to sql commit. The DB is Oracle XE 10g.
"Error occurred while exporting to Reporting Schema.See the log file for details"
2011-11-12 06:33:45,859 [Thread-11] ERROR ReportsHandler - Error Exporting to Reporting Schema:
java.lang.NullPointerException
     at oracle.dbtools.crest.model.xtdmapping.XtdMapping.isOwnerDesignPartLoaded(Unknown Source)
     at oracle.dbtools.crest.model.xtdmapping.XtdMapping.getOwnerObject(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSMappings.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
Environment
About
Oracle SQL Developer Data Modeler 3.0.0.665
Version 3.0.0.665
Build 665
Copyright © 2008,2010 Oracle. All Rights Reserved.
IDE Version: 11.1.1.4.37.59.36
Product ID: oracle.datamodeler
Product Version: 3.0.0.665
Version
Component     Version
=========     =======
Java(TM) Platform     1.6.0_23
Oracle IDE     3.0.0.665
Versioning Support     3.0.0.665

Hi,
you can try Data Modeler 3.1 EA1 (available here http://www.oracle.com/technetwork/developer-tools/datamodeler/overview/index.html) or EA2 when it's published - mappings problem is fixed there.
Philip

JAVA error when exporting to reporting schema ODDM 4.1

When attempting to export a design to a reporting schema, we received the following error:
ERROR ReportsHandler - error exporting to reporting schema:
java.lang.classcastException: oracle.dbtools.crest.model.design.relational.column cannot be cast to oracle.dbtools.crest.model..design..relational.columnView
at oracle.dbtools.crest.exports.reports.RSViewColumn.export (RSViewColumns.java:43
at oracle.dbtools.crest.exports.reports.RSRelationalModel.export (RSRelationalModel.java:62)
at oracle.dbtools.crest.exports.reports.ReportsHandler.export (ReportsHandler.java:135)
at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run (ControllerApplication.java:2079)
We downloaded and installed ODDM 4.1 (EA-1) build 4.1.0.866 to resolve an issue with column widths when exporting to the reporting schema (per SR 3-10154440761). This is the 64 bit version with the included JAVA 1.8 JRE.

David,
We migrated this model from data modeler 3.3. That Model was created from an import from Oracle Designer. We have not yet tried to import the data model from Oracle Designer directly into v4.1 but are planning to do so shortly. When we tried to export that design (from v3.3) to the reporting schema, it failed with object too large for column errors. We wrote SR 3-10154440761 and were advised by Michael Wickham to use v4.1 EA as the column size issue had been resolved in this version. It was apparent that the export to the reporting schema was making more progress before it failed on the JAVA error.
We are trying to migrate from Oracle designer to Oracle Data Modeler

Cannot export to reporting schema (File - Export - To Reporting Schema )

I just installed SQL Data Modeler version 2.0.0 Build 584
Export to reporting schema (File -> Export -> To Reporting Schema ) is not working.
I created a report schema and tried to export the Sql Data Modeler (SDM) repository to the Oracle schema.
I received the following error from SDM: "Error occured while exporting to Reporting Schema. See the log for details".
I checked the log ( View -> Log ) and all the log contained was "2010-01-18 11:10:23 - Exporting to Reports Schema"
The reports schema contained 44 tables. None of the tables contain any data.
I can create a test table and add data to it in the reporting schema. There is lots of quota available to the reports schema.
I have tried the report export to Oracle several times with the former version with mixed results.
Any suggestion? Does the "export to reporting schema" work for anyone else?
The following script from TOAD describes the reports schema.
CREATE USER SDM_REPORT
IDENTIFIED BY <password>
DEFAULT TABLESPACE USERS
TEMPORARY TABLESPACE TEMP
PROFILE DEFAULT
ACCOUNT UNLOCK;
-- 2 Roles for SDM_REPORT
GRANT CONNECT TO SDM_REPORT;
GRANT RESOURCE TO SDM_REPORT;
ALTER USER SDM_REPORT DEFAULT ROLE ALL;
-- 15 System Privileges for SDM_REPORT
GRANT CREATE TRIGGER TO SDM_REPORT;
GRANT CREATE PROCEDURE TO SDM_REPORT;
GRANT DROP PUBLIC SYNONYM TO SDM_REPORT;
GRANT DEBUG CONNECT SESSION TO SDM_REPORT;
GRANT CREATE MATERIALIZED VIEW TO SDM_REPORT;
GRANT CREATE TABLE TO SDM_REPORT;
GRANT CREATE SESSION TO SDM_REPORT;
GRANT SELECT ANY DICTIONARY TO SDM_REPORT;
GRANT CREATE ROLE TO SDM_REPORT;
GRANT CREATE VIEW TO SDM_REPORT;
GRANT CREATE TYPE TO SDM_REPORT;
GRANT CREATE SEQUENCE TO SDM_REPORT;
GRANT CREATE PUBLIC SYNONYM TO SDM_REPORT;
GRANT CREATE ANY SYNONYM TO SDM_REPORT;
GRANT UNLIMITED TABLESPACE TO SDM_REPORT;
-- 1 Tablespace Quota for SDM_REPORT
ALTER USER SDM_REPORT QUOTA UNLIMITED ON USERS;

Problem solved: Data Modeler would export other designs to an Oracle schema but not the one I was working on (Babylon). I saved a copy of Babylon, BabylonReports and deleted everything except the relational model. Then I could export it to the repository. I assume that either the logical model or dataflow model had a problem which prevented Data Modeler from saving the export. Next time I'll run Design Rules to see if there is an error I can eliminate that will allow me to save an export.

EA2:Error on Export to Reporting Schema

While i was trying to export the created desing to the reporting schema, found the below error in the log.
2010-11-29 16:01:26,741 [Thread-56] ERROR ReportsHandler - Error Exporting to Reporting Schema:
java.sql.SQLException: ORA-12704: character set mismatch
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)
     at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)
     at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)
     at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
     at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)
     at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)
     at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1008)
     at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1307)
     at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3449)
     at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3530)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
     at oracle.dbtools.crest.exports.reports.RSCommentsInRDBMS.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSEntities.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.RSLogicalModel.export(Unknown Source)
     at oracle.dbtools.crest.exports.reports.ReportsHandler.export(Unknown Source)
     at oracle.dbtools.crest.swingui.ControllerApplication$ExportToReportsSchema$1.run(Unknown Source)
Can someone help me understanding what is going wrong here or suggest on what should be characterset defined for the database.

From the stack trace it appears that the problem area is the "Comments in RDBMS" in one of the Entities in the Logical Model.
Are there any special characters in any of these text panels?

SQL Developer Data Modeler - Version 3.0.0.665 - Open older project fail

Hi,
I just downloaded latest version of SQL Developer Data Modeler (3.0.0.665) and there is no "File" -> "Open" menu item. There is only "Save", "Save as", "Compare with" and "Exit".
I try to drag`n`drop project file to the Data Modeler window. This operation leads to opening project file as XML. I got the same result when I try to open the file with windows context menu "Open with".
How can I open older Data Modeler project? My previous version was 3.0.0 and project file was created there.
Maybe I need disable "Start Page'? But how? I cann`t find appropriate param in Tools -> Preferences

Hi,
See this thread: Re: 30EA2 problem: Menu items not available
Ivan

SQL DEV DATA MODELER VERSION CONTROL

Hi Anyone can tell me how to setup an environment to do version controlling with sql DEV data modeler.
Thanks

Hi,
you can use visualSVN server - it has a free edition http://www.visualsvn.com/server/
and getting started is here http://www.visualsvn.com/server/getting-started/
Philip

EXPORT/IMPORT SBO SCHEMA ERROR

Hello,
We have a client who is working with SAP BusinessOne version for HANA, with HANA PLATFORM rev. 69 and I need to export your database and import it to our development server .
To backup/restore the database I have performed the following steps :
1 - I have made the export of a ' SCHEMA ' with "EXPORT "SBOXXX_ES"."*" AS BINARY INTO '/tmp/SBOXXX_ES' WITH REPLACE THREADS 10;".
2 - I have compressed files in Linux using the command : tar- czvf .....
3 - I've Unzipped the files to our local server.
4 - Performing the ' IMPORT ' command gives me the following errors,I tried two ways to import :
4.1 - IMPORT "SBOGXXX_ES"."*" as binary from '/tmp/SBOXXX_ES' with replace threads 10 rename schema "SBOXXX_ES" to "SBOXXX_ES_2";
Error mesage: SAP DBTech JDBC: [2]: general error: [Other schema]._SYS_SS_CE_1957622_RET not found in the import directory.
4.2 - IMPORT "SBOXXX_ES"."*" as binary from '/tmp/SBOXXX_ES'
with replace threads 10 NO DEPENDENCIES
rename schema "SBOXXX_ES" to "SBOXXX_ES_2";
Error mesage: SAP DBTech JDBC: [2048]: column store error: table import failed: [30111] Binary import failed (could not execute create statement);invalid column view: ODLN: line 7 col 45 (at pos 506) at ptime/query/checker/check_cube.cc:259
I guess when you export the " SCHEMA " exported la la " DEPENDENCIES ON" option and these are generating the first error when importing .
If the error is of the DEPENDENCIES, in which DEPENDENCIES are stored files to edit , and remove all that is giving the error (SYS_SS_CE_1957622_RET ) .
Thank you very much for your support .
Adria.

Hi Adria,
I asked you to test the import on the system you exported from to determine if the problem is occurring because you are transporting the files from system 1 to system 2. If it works on point of origin we should investigate why the transfer is corrupting the file. I thought it would be ok because you are renaming the schema as part of the process. I would not want to import @point of origin without the rename.
Whenever some one asks me how to export a schema and import it with a different name I provide:
export "SBODEMOGB"."*" as
binary into '/home/SBODEMOGB' with replace threads 10;
import "SBODEMOGB "."*" as
binary from '/home/SBODEMOGB_901' with replace threads 10 rename schema "SBODEMOGB" to
"SBODEMOGB_NEW";
You are using the statement I would provide.
I cannot find an hints for the error reported (SYS_SS_CE_1957622_RET). If you do not see anything more helpful in the trace file I would suggest opening a customer message.
Best regards,
Duncan

Data model automatically changes the color and the report corrupts.

we want to run six reports in a single report and users can run the report they select . So,We have 23 simple queries in datamodel and 20 pages of layout,
it was working fine.but now if we make some changes the color in the datatmodel changes,when we try to save this the file corrupts.when we try to open the
file it says some information missing in the report.we have reports builder10g.Is there any size limit for rdf file? because our rdf file size 944kb.
Thank you.

No.

Data modeler, error when exporting to csv files

hi, i have a relational model and i need to export this model to csv files, when exporting the model it errors,
displaying the following error nmessage:
Oracle SQL Developer Data Modeler Version: 2.0.0 Build: 584
Oracle SQL Developer Data Modeler Export Log
Date and Time: 2010-09-21 15:17:17
Design Name: Diagram
Model Name: CSV
Export Finished
Errors: 1
Warnings:0
<<<<< ERRORS >>>>>
java.lang.NullPointerException
the issue is a file is missing when exporting proccess is done, the file is DM_CommentsRDBMS.csv, this file contains the commens of columns.
Thanks.

Hi,
I logged bug however information is not enough to locate the problem.
You can use export to reporting schema in order to get your model exported - in database in that case.
We are not going to extend "export to CSV file" functionality any further - it'll be as it is now.
Philip

Latest PowerQuery issues with data load to data models built with older version + issue when query is changed

We have a tool built in excel + Powerquery version 2.18.3874.242 - 32 Bit (No PowerPivot) using data load to data model (not to workbook). There are data filters linked to excel cells, inserted in OData query before data is pulled.
The Excel tool uses organisational credentials to authenticate.
System config: Win 8.1, Office 2013 (32 bit)
The tool runs for all users as long as they do not upgrade to PowerQuery_2.20.3945.242 (32-bit).
Once upgraded users can no longer get the data to load to the Model. Data still loads to the Workbook but the model breaks down. Resetting load to data model erases all measures.
Here are the exact errors users get:
1. [DataSource.Error] Cannot parse OData response result. Error: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2. The Data Model table could not be refreshed: There isn't enough memory to complete this action. Try using less data or closing other applications. To increase memory available, consider ......

Hi Nitin,
Is this still an issue? If so, can you kindly provide the details that Hadeel has asked for?
Regards,
Michael Amadi
Please use the 'Mark as answer' link to mark a post that answers your question. If you find a reply helpful, please remember to vote it as helpful :)
Website: http://www.nimblelearn.com, Twitter:
@nimblelearn

Invalid Name Pattern in SQL Developer Data Modeler

I am using Data Modeler version 3.3.0.747, I have exported a couple of data models (logical and physical) to an Oracle 11.2.0.3 database. I used the Reporting_Schema_Permissions.sql file to define the ID that owns the repository. Each data model that I exported returned the successful export message.
However when I use Oracle Data Modeler and connect (as a different user) to the repository to generate a report on one of the diagrams I immediately get an error returned. The error is (from the log file in datamodeler\log\datamodeler.log):
2013-04-19 08:36:12,233 [Thread-18] ERROR ReportsGenerationDialog - Generating report from Reporting Schema exception - invalid name pattern: username.OBJECTS_LIST
Where username is the name of the ID being used to generate the report (not the repository owner ID).
I have created public synonyms on the repository tables and views (though I must have missed where that was a requirement) so the repository objects can be seen by other users.
Has anyone encountered this and if so how did you resolve it. I have searched the web (and the Oracle forums) and so far had no hits on this issue. That seems to indicate that there is something I must have missed in the setup or such.
Thanks

Hi,
I think you didn't grant EXECUTE to package and types. Here is full working script:
DECLARE
CURSOR cur IS SELECT table_name, owner FROM all_tables WHERE owner='<owner>';
BEGIN
FOR rec IN cur LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON '||'<owner>'||'.'||rec.table_name||' to '||'<another_user>';
EXECUTE IMMEDIATE 'CREATE SYNONYM '||'<another_user>'||'.'||rec.table_name||' FOR '||'<owner>'||'.'||rec.table_name;
END LOOP;
END;
DECLARE
CURSOR cur IS SELECT view_name FROM all_views WHERE owner='<owner>';
BEGIN
FOR rec IN cur LOOP
EXECUTE IMMEDIATE 'GRANT SELECT ON '||'<owner>'||'.'||rec.view_name||' to '||'<another_user>';
EXECUTE IMMEDIATE 'CREATE SYNONYM '||'<another_user>'||'.'||rec.view_name||' FOR '||'<owner>'||'.'||rec.view_name;
END LOOP;
END;
DECLARE
CURSOR cur IS SELECT type_name FROM all_types WHERE owner='<owner>';
BEGIN
FOR rec IN cur LOOP
EXECUTE IMMEDIATE 'GRANT EXECUTE ON '||'<owner>'||'.'||rec.type_name||' to '||'<another_user>';
EXECUTE IMMEDIATE 'CREATE SYNONYM '||'<another_user>'||'.'||rec.type_name||' FOR '||'<owner>'||'.'||rec.type_name;
END LOOP;
END;
GRANT EXECUTE ON <owner>.pkg_osdm_utils to <another_user>;
CREATE SYNONYM <another_user>.pkg_osdm_utils FOR <owner>.pkg_osdm_utils;
There is no document for reporting repository install process. If you are exporting design for first time, the repository is automatically created for you.
When you get new version of DM you can
1. Use new repository
2. Upgrade existing one. If so, the simplest variant is to run /datamodeler/reports/DMRS_Upgrade_Script_<latest_vesrion>. Eventually compile single stored procedure.
Another variant for upgrade is with running osddm_upgr.sql, but there is some error, which is going to be fixed in the next release.

SQL Developer Data Modeler Repository

Hi,
I would like to know how to save all my applications into the Data Modeler Repository instead of doing it piece by piece and having to create a dmd file for every single application I imported into Data Modeler.
In Oracle Designer, everything is in the repository and I can run reports against the tables and views belonging to that repository. So, I can produce a pdf documentation out of it. Can we do the same with Data Modeler?
Thank you!

Hello Anonymous,
I'll start with your first comment - "I would like to know how to save all my applications into the Data Modeler Repository ". The Repository is just for reporting purposes, as Dimitar points outs, so saving all your applications in the Data Modeler is merely File - Save. This action saves the current design (with all its models) to the file system. The main premise here is that the Data Modeler is a file based product and all models and designs are saved locally to the file system. This is a positive move for many customers who are now building applications in Java or using any of the application development environments that work with a variety of files. They are taking all the artifacts and placing them under version control using open source versing tools like Subversion. Using the Data Modeler, they can do the same.
For reporting you have a choice, one of which has also been explained. The action of creating a schema before you export the design is a one off step. Following on from this you can export new versions of the model to the same repository. The reason we did this was that many of the Designer audience wanted to write and run their own reports. So here you have a set of tables that you can write whatever SQL query you want to use.
The other reporting option is to use the integrated reports in the product and you do not have to export the design or open another product or write SQL.
Have you used the Design Rules in the Data Modeler? These are a set of "reports" for quality assurance purposes. There are many of these reports at all levels of the design which verify that your model is defined according to a set of database rules and general business rules and if you like, you can add your own rules.
I attended ODTUG last week in LA and was really pleased to listen to a number of talks by well seasoned Designer users who have successfully transitioned to the Data Modeler and who had many positive experiences.
Yes, the tools are different - but the one tool was not designed to replace the other - Data Modeler does none of the application design and generation that Designer does, those customers who have wanted to replace one tool (people are moving to the data Modeler from different tools) with the Data Modeler, have reported to me that they are pleased with the change.
Regards
Sue Harper
Product Manager

SQL Developer Data Modeler not drawing foreign key relationships

I'm having trouble with SQL Developer Data Modeler when I importa a DDL that has foreign keys. I export DDL files from SQL developer and choose various subsets of files. Sometimes Data Modeler will not recognize a foreign key if I include say a dozen files in the DDL file, but it will if I include just a few. Worse, even if the foreign key is recognized, sometimes it is not drawn in the Data Modeler and I have no way to make it be drawn. To be specific, I import a file containing the DDL for just two tables -- I see the foreign key! I import a file containing the DDL for a dozen tables including the two, I don't! Is there something I am not understanding about when Data Modeler will draw foreign keys or is the tool simply quite buggy?
Much thanks!
-ttamon

Hi Philip,
I believe I have isolated the problem. Apparently if a field is named "FOREIGN..." it interferes with the tool recognizing foreign keys. Try to import a DDL file containing the following text:
CREATE TABLE "SAMPLE"."SAMPLE_ONE"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "VALUE" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ;
CREATE TABLE "SAMPLE"."SAMPLE_TWO"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "FOREIGN_NAME" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ;
CREATE TABLE "SAMPLE"."SAMPLE_THREE"
(     "ID" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "VALUE" VARCHAR2(255 CHAR) NOT NULL ENABLE,
     "ALT_ID" VARCHAR2(255 CHAR),
     PRIMARY KEY ("ID")
TABLESPACE "SAMPLE_DATA" ENABLE,
     CONSTRAINT "FK6DF8294F2288190D" FOREIGN KEY ("ALT_ID")
     REFERENCES "SAMPLE"."SAMPLE_ONE" ("ID") ENABLE
TABLESPACE "SAMPLE_DATA" ;
You will discover the foreign key is not recognized or drawn! Now, if you swap the location of the third table (put it up first) everything works fine. This is how I discovered the problem, various subsets would work, others would not. To confirm the problem is with the field named "FOREIGN_NAME" use the DDL as specified above but change the first letter in the word "FOREIGN" to something else, and it will recognize the foreign key. Looks like a bug to me (took me about 4 hours to isolate this!). I am using Oracle SQL Developer Data Modeler version 2.0.0 Build 584.
-ttamon

Data Modeler version 2.0.0 - Export to reporting schema error

Similar Messages

Maybe you are looking for