Oracle SQL Developer Data Modeler - Release
Notes
1 July 2009
Oracle SQL Developer Data Modeler allows you 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, Import 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. For more detail of the feature
see the collateral provided on the Data
Modeler home page on the Oracle Technology Network.
Installing
Download and unzip the files into a new and empty
directory. Do not unzip over any existing early adopter installations,
should you have them. If you want to save your settings, such as the Default
Design Directory and Formatting Options, save the \datamodeler\bin\settings.xml
file.
Builds for the Mac, Linux and Windows without JRE
are all the same download. The required executables are available in the
same zip.
For Linux and Mac OS X installations download the file
without the JRE. When prompted, direct the install to your JRE
1.6 directory. If JRE 1.5 is already installed and is the default, you
will not be prompted. In this case edit the datamodeler.conf file in the
\datamodeler\bin directory and add SetJavaHome. (e.g. SetJavaHome /usr/lib/jdk16_04)
Importing Former Settings
(DEFAULTS) after you install a new build
In SQL Developer Data Modeler you can set some DEFAULT settings in the
Tools > General Options menu. For example, the Default
Design Directory and Formatting Options. After installing a new build,
you can use the Import/Export function
in the Tools General Options menu to
import the settings.xml file.
Save As
If you worked with an early adopter release,
and want to preserve and open your models in the production release, then
save your work by using "Save As" before you start making changes
in the production release.
Printing
You can print your diagrams to a number of file
formats, including PDF, PNG, JPG, 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 OBE
that'll walk you through creating and accessing the repository repository
and running the reports.
Providing Full Support for
Oracle Database 11g features
Full support for Oracle Database 11g will be added in time. The current
Oracle Database 11g implementation is Oracle Database 10g compatible.
Oracle Designer Import
SQL Developer Data Modeler connects to and imports directly from the Oracle
Designer repository. The focus of this import is the Data and not Application
design. At this stage the Data Modeler does not import table spaces, stored
procedures, packages, functions and data flow diagrams.
Domains
SQL Developer Data Modeler does
not include a default domains file.
NOTE: This is a change from the early adopter releases which
had a predefined domains file. This file still exists in the \datamodeler\domains
directory and can be imported to provide a default set of values if required.
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.
To create a named domains file, select Tools
> Domains Administration and click the Select button, next
to the Domains File field. Type in a new file name and click open. Now
you can add all the new domains to this file as described. In order to
use the new file you need to import these domains into your current design,
otherwise the default domains file is used.To import a domains file. select
File > Import > Domains. You can accept all the domains or select
those you want to import individually.
Oracle SQL Developer Data Modeler runs on the following
operating systems:
- Microsoft Windows (XP, Vista)
- Linux
- Mac OS
The following requirements must be met to install and
run correctly:
- JavaTM 1.6 or higher Standard Edition Runtime Environment
- About 125 MB on Hard Disk
- 512 MB at a minimum, 1 GB RAM is recommended
Note: We provide the download with
and without the Java Runtime. Minimum is JRE 1.6. For Linux and Mac install
you must download the zip without the JRE. You'll be prompted on startup
for the path to the JRE.
Database Imports
Oracle SQL Developer Data Modeler imports from:
- Supported Oracle Databases, Microsoft SQL Server
2000 or 2005, DB2/LUW V7 or V8 script file
- Supported Oracle Databases, Microsoft SQL Server2000
or 2005, IBM DB2/LUW V7 or V8, 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 drivers can be downloaded from the following links:
- 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:
- The driver for ODBC/JDBC is included in Java, so
there is nothing extra to install
To add the drivers yourself: Go to Tools - >
General Options -> DDL -> Third Party JDBC drivers
After installing, the drivers must be set in the option
dialog as follows:
- SQL Server 2000 - msbase.jar, mssqlserver.jar, msutil.jar
- SQL Server 2005 - sqljdbc.jar
- DB2/UDB
- db2jcc.jar
From Other Modeling Tools
- SQL Developer Data Modeler
imports the following Oracle Designer objects:
- 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 subview in relational model
- Each diagram that contains entities is transformed
into subview in logical model
- Each diagram that contains object (structured)
types is transformed into subview in Data Types model
- SQL Developer Data Modeler supports the imports from
the following:
- CA Erwin Data Modeler, version 4.x
- Sterling COOL:DBA V2.1, Sterling Bsnteam V7.2 and
Cayenne Bsnteam V7.2 formats
- For Multi-Dimensional Models
- SQL Developer Data Modeler imports
- Oracle SQL Developer Data Modeler models
- Domains files
- Supported Oracle Databases
- Microsoft SQL Server 2000 or 2005
- IBM DB2/LUW V7 and V8 script file
- Multi-dimensional support
- Cube View Metadata
- XMLA and Oracle ROLAP and MOLAP (AW)
- CSV file
We are aware of the following limitations and issues.
This list is not exhaustive, but a list of issues that you may encounter.
Please contact Oracle Support through Metalink
for further queries about issues, or to log new issues.
- Note for designs created with earlier versions of
Data Modeler – persistence has changed and it’s strongly
recommended that you use the “Save As” functionality to
create new version of designs
- The wizard to assign domains as a data type for group
of attributes and columns has not been exposed, you should assign domains
using the column or attribute properties dialog
- Colored syntax in generated scripts can cause a
delay for large scripts. A workaround for script files greater than
1 Mb has been implemented in DDL file editor. These files are displayed
without colored syntax. This is not available for the DDL preview for
selected objects in the relational model.
- If a database import takes too long, it may be either
be a memory problem, related to the network or database. To check if
it's memory related, open the datamodeler.conf file in the datamodeler\bin
directory. Check the – “AddVMOption -Xmx768M” –
if the import is slow and used memory is close to this given value,
then you have a memory problem. You can increase the value, by changing
the value in the conf file and restarting. Use a memory setting as much
as needed to complete import.
- Partitioning is not transferred when cloning a DB2/390
v.7 site to DB2/390 v.8 site. This is due to the different kind of partitioning
- index controlled in v.7 and table controlled in v.8. As workaround,
generate v.7 DDL and import it using “Import Storage Objects from
DDL” functionality available in the DB2/390 physical model node.
The index controlled partitioning is transformed into table controlled
during the import
- Merging physical objects as part of the merge of
relational models. The properties of the objects in the source model
override the properties of objects with the same name and type in target
(current) model. For example, the source tablespace “Users”
with one data file and target tablespace “Users” with two
data files. the result after the merge is a tablespace “Users”
with one data file and all properties of source tablespace and data
file.
You can use the documentation in the Oracle SQL Developer
Data Modeler Help or access the online
documentation.
|
Bookmark
