Oracle SQL Developer Data Modeler 4.0 Release Notes

December 2013



Oracle SQL Developer Data Modeler is a free data modeling and design tool used to increase developer productivity by providing the means to develop logical, multi-dimensional, user defined data types, relational and physical data models. The tool provides full forward engineering, including engineering from Logical ERD models to Relational models and the reverse, importing from the Data Dictionary and DDL script generation. The Data Modeler imports from and exports to a variety of sources and targets, provides a variety of formatting options and validates the models through a predefined set of design rules. See what's new in SQL Developer Data Modeler 4.0 New Features.

Platform Support and System Requirements

Oracle SQL Developer Data Modeler runs on the following operating systems:

- Microsoft Windows (XP, Vista, Windows 7 including x64)
- Linux
- Mac OS X

The following requirements must be met to install and run correctly:

- JavaTM 1.7 or higher Standard Edition Runtime Environment
- About 125 MB on Hard Disk
- 512 MB at a minimum, 1 GB RAM is recommended

- We provide the download with and without the Java Runtime. If you download the files without the Java Runtime, you'll be prompted on startup for the path for the JRE. The minimum is JRE 1.7.
- For the Linux install, download the .rpm file. For the Mac install, download the macosx.tar.gz file.

Before You Start

Before Installing

If you have worked with the production release of SQL Developer Data Modeler 2.0, then you can save and reuse the default settings you made in the Tools > General Options menu, such as the Default Design Directory and Formatting Options. After installing SQL Developer Data Modeler 4.0, you can use the Import/Export function in the Tools > Preferences > Data Modeler menu to import the \datamodeler\bin\settings.xml file.

You need to copy types.xml and defaultRDBMSSites.xml files from datamodeler\datamodeler\types directory to directory set as default system types directory in preferences when preferences are migrated from earlier version.


  • Download and unzip the files into a new and empty directory. Do not unzip over any existing installations, should you have them.
  • For downloaded files that do not include a JRE. When prompted, direct the install to your JRE 1.7 directory. If JRE 1.7 is already installed and is the default, you will not be prompted. In this case edit the datamodeler.conf file in the \datamodeler\datamodeler\bin directory and add SetJavaHome. (e.g. SetJavaHome /usr/lib/jdk17)
  • 64-Bit Support: SQL Developer Data Modeler is supported on 64-bit platforms, ensure you use the 64-bit executable available in the zip file. If you use the 64-bit Data Modeler executable, you will need to use a 64-bit JRE.

Using Save As

If you want to open models built in SQL Developer Data Modeler 2.0 and 3.0, you must use "Save As" before you start making changes in the SQL Developer Data Modeler 4.0.

SQL Developer Data Modeler 4.0 can open designs created with 3.1.x version and save them in their original location however further maintenance of such design in Data Modeler 3.1.x version is not recommended due possible lost of information.


You can print your diagrams to a number of file formats, including PDF, PNG, JPG.
Note: Version 4.0 does not support printing to SVG.

Using the Reporting Repository

You can export your designs to a reporting repository. Read the online help or the FAQ for more information. There is a brief Oracle by Example tutorial that walks you through creating and accessing the reporting repository and running the reports. Search for "Data Modeler" in the Oracle Learning Library for all tutorials.
Note: The reporting schema has been updated and so you can use the update scripts (located in the installation directory, \datamodeler\reports) and depending on your version of repository (starting with version 2.0) to apply related scripts to upgrade it to version 4.0. The update script is not required when an existing repository is deleted and a new repository is created.

SQL Developer Data Modeler 4.0 reporting repository is also supported on Oracle Database Express Edition 11g.


Custom reports cannot be exported to RTF.

Oracle Designer Import

SQL Developer Data Modeler connects to and imports directly from the Oracle Designer repository.

The following is a list of supported imports from Oracle Designer

  • Domains, object (structured) types, collection types
  • Entities, relationships, arcs, entity inheritance hierarchies
  • Tables, views, foreign keys, arcs
  • Triggers for tables and views
  • Snapshots, clusters, synonyms, sequences
  • Each diagram that contains tables is transformed into a subview in the Relational model
  • Each diagram that contains entities is transformed into a subview in the Logical model
  • Each diagram that contains object (structured) types is transformed into a subview in the Data Types model
  • SQL Developer Data Modeler does not import tablespaces, stored procedures, packages, functions and data flow diagrams from the Oracle Designer Repository. (Support for these are planned for a future release) As these structures are supported in the product, users can import these definitions into SQL Developer Data Modeler by connecting directly to the Oracle Data Dictionary.


  • SQL Developer Data Modeler does not include a default domains file.
  • To create new domain definitions, select Tools > Domains Administration and click Add to create and add your own domains. These domains are added to the default file, defaultdomains.xml and can be used for all your projects.

Comparing Logical Models

To compare two logical models, ensure you have one model open and then select File > Import > Data Modeler Design. You can now select the logical model for the comparison. Once you have made the selection, you are presented with the Compare Merge dialog.

Comparing Relational Models and Generation Alter DDL scripts

  • To compare two relational models, ensure you have one relational model open in the design and then select File > Import > Data Dictionary (or DDL). In the import dialog you get the choice to "Swap Target Model". This drives the point of truth and the resulting merge compare dialog. You can elect either to merge the models or to View DDL to see the DDL to update the data dictionary.
  • The current model can also be compared to another Data Modeler design using Tools > Compare /Merge Models.


All passwords set in the physical model are encrypted when saving a design in the file system.

Delete Rules

The Tools > Preferences >Data Modeler > Model > Relational >Default Foreign Key Delete Rule defines the delete rule when a new FK is created. If you create a model by importing a DDL script, then ensure the option is set as required before the import.

Cloning Physical Models

When cloning the physical details from one model to another, ensure you have saved the database you want to clone from. Note you can only clone databases of the same release or lower. i.e. to populate a new Oracle Database 11g physical model, you can select a saved Oracle Database 11g or earlier.

Adding a Design to a Subversion Repository

You can add your design to a Subversion repository using a few different approaches; either from within SQL Developer Data Modeler, or by using a separate client.

  • If you save the full design to the Subversion repository using another tool, then when you open SQL Developer Data Modeler, check out the design and commit the design immediately. This commit action sets the repository property against the design within the product.
  • You are advised to add your designs to the Subversion repository from within the Data Modeler.
    • Create a new remote directory in the Data Modeler and check that out.
    • Open your design in the Data Modeler and save it to the checked out directory. This action sets the repository property against the design within the product and your design is now under version control.

IMPORTANT: A design should be fully saved before commit, update and merge operations are done. It is recommended to close and reopen the design after update or merge operations are completed, especially when conflicts are resolved. Do not save design during or after update or merge operations.

For more information on using Subversion with SQL Developer Data Modeler see the Documentation and the online demonstrations available.

Creating User Defined Design Rules and Transformations

SQL Developer Data Modeler allows users to build scripts for user defined design rules and transformations. Object properties are described in "datamodeler/datamodeler/xmlmetadata/doc" directory; use index.html.

The product provides a few samples as illustrations of user defined design rules and transformations. For more information see the Documentation and the online demonstrations available.

Supported Import formats

From Other Modeling Tools

    - Oracle Designer 9i and above
    - CA Erwin Data Modeler 4.x and 7.x
    - Sterling COOL: DBA V2.1, Sterling Bsnteam V7.2 and Cayenne Bsnteam V7.2 formats
    - For Multi-Dimensional Models
         Cube Views metadata

Database Imports

Oracle SQL Developer Data Modeler imports from:

- Supported Oracle Databases, Microsoft SQL Server2000 or 2005, IBM DB2/LUW V7 or V8, IBM DB2 for OS/390 and z/OS and ODBC/JDBC compliant data dictionary

IMPORTANT: Oracle does not ship the non-Oracle drivers.To access the non-Oracle databases, you need to download and add the drivers required.

The following drivers will need to be download:

- For Microsoft SQL Server:
   SQL Server 2000 - For SQL Server 2000 you must make sure you have installed all three .jar files: msbase.jar, mssqlserver.jar and msutil.jar
   SQL Server 2005 - The drivers for SQL Server 2000 can be used for import from SQL Server 2005 database
- For DB2/LUW - IBM Data Server Driver for JDBC and SQLJ
- The driver for ODBC/JDBC is included in Java, so there is nothing extra to install

To add the drivers yourself: Go to Tools > Preferences > Data Modeler > Third Party JDBC drivers

After installing, the drivers must be set in the Preferences dialog as follows:

- SQL Server 2000 - msbase.jar, mssqlserver.jar, msutil.jar
- SQL Server 2005 - sqljdbc.jar
- DB2/UDB            - db2jcc.jar

Supported Export formats

- Supported Oracle Databases
- Microsoft SQL Server 2000 or 2005
- IBM DB2 V7 and V8 script file
- Multi-dimensional support
    Cube View Metadata
    XMLA and Oracle ROLAP and MOLAP (AW)
- CSV file


SQL Developer Data Modeler is supported through My Oracle Support for all users with an Oracle Database support license.


You can use the documentation in the Oracle SQL Developer Data Modeler Help or access the online documentation.

Finding More Information

Visit Oracle SQL Developer Data Modeler on OTN for more information. Use the Oracle SQL Developer Data Modeler Forum for any discussion or queries.