Home > Data Modeler Concepts and U... > Data Modeler Reports
You can view reports on Data Modeler objects in the following ways:
Generate reports as XML files (Microsoft Word format) on your local drive, and then open the XML files. For more information, see Generating Reports as XML Files.
Use SQL Developer to view reports based on information in the Data Modeler reporting repository. For more information, see Using SQL Developer to View Exported Reporting Schema Data.
You can save individual reports as XML files (in Microsoft Word 2003 and later XML format) and then view each report. The reports are stored in the location specified or defaulted for Default Reports Directory under Data Modeler preferences.
Data Modeler ensures unique names for each file; for example, if you generate a report on all table and if AllTablesDetails_1.xml
already exists, AllTablesDetails
_2
.xml
is created. (If you generate report files from the reporting repository in the reporting schema, the file names include _rs, for example, AllTablesDetails_1_rs.xml
.)
You can generate report files using either of the following approaches:
Generate reports based on currently loaded designs. (This approach does not involve creating or using a reporting schema and reporting repository.)
Generate reports based on information in the reporting repository in the reporting schema (which are explained in Reporting Repository and Reporting Schema).
To generate and view a report stored as an XML file, follow these steps:
Click File, then Reports.
For Available Reports, select one of the types of objects for which to report information: Tables, Entities, Domains, Glossaries.
Optionally, select Include All Objects to have the report contain information about all objects of the selected type.
If you do not select Include All Objects, you will be able to click Select beside Selected Object on the Loaded Designs tab to select an object by name.
Click one of the following tabs (if the desired tab is not already selected):
Loaded Designs, to generate a report based on one or more currently loaded Data Modeler designs
Reporting Schema, to generate a report based on designs in the reporting repository in the reporting schema
For Available Designs, select the desired Data Modeler design.
For Available Models, select the desired model. (The list of models reflects the type of objects for the report.)
For Selected Object (only if you did not specify Include All Objects), click Select to specify the object to be reported on.
Click Generate Report.
A message is displayed with the location and name of the XML file for the report.
Go to the XML file and open it.
Related Topics
You can the reports feature in Oracle SQL Developer to view information that has been exported to the Data Modeler reporting repository. To export the information about a design to the reporting repository, follow the instructions in Reporting Repository and Reporting Schema.
To view the reports in SQL Developer, you must do the following:
In SQL Developer, check to see if the Reports navigator already includes a child node named Data Modeler Reports. If it does include that node, go to the next step; if it does not include that node, install the Data Modeler Reports extension, as follows:
Click Help, then Check for Updates. In the Check for Updates wizard, specify Install From Local File, and specify the following local file in the location where you installed Data Modeler: datamodeler\reports\oracle.sqldeveloper.datamodeler_reports.nn.nn.zip (Windows systems) or datamodeler/reports/oracle.sqldeveloper.datamodeler_reports.nn.nn.zip (Linux systems), where nn.nn reflects a build number.
In SQL Developer, open the Reports navigator, expand the Data Modeler Reports node, plus nodes under it as desired.
For each report that you want to view:
Double-click the node for the report name.
Select the database connection that you used for the reporting repository.
Complete the Bind Variables dialog information, and click OK. For the bind variables, the default values represent the most typical case: display all available information for the most recent version of the design.
The bind variables enable you to restrict the output. The default value for most bind variables is null, which implies no further restrictions. To specify a bind variable, select the variable name and type an entry in the Value field. Any bind variable values that you enter are case insensitive. Bind variable values can contain the special characters %
(percent sign) to mean any string and _
(underscore) to mean any character.
Data Modeler reports are grouped in the following categories:
Design Content reports list information about the design content (objects in the design).
Design Rules reports list information about the design rules as they apply to the logical and relational models.
Design Content reports list information about the design content (objects in the design).
Data Types Model: Contains reports related to the Data Types Model.
Logical Model: Contains reports related to the Logical Model.
Relational Model: Contains reports related to the Relational Models.
Related Topics
Design Rules reports list information about the design rules as they apply to the logical and relational models. (See the information about the Design Rules dialog box.)
Logical Model: Contains reports related to the Logical Model.
Relational Model: Contains reports related to the Relational Models.
Related Topics
The Data Modeler reporting repository is a collection of database schema objects for storing metadata and data about Data Modeler designs. The schema in which the reporting repository is stored is called the reporting schema.
It is recommended that you create a separate database user for the Data Modeler reporting repository, and use that schema only for the reporting repository. For example, create a user named DM_REPORT_REPOS, and grant that user at least CONNECT and RESOURCE privileges. (You can create the reporting repository in an existing schema that is also used for other purposes, but you might find that more confusing to keep track of.)
Note: If you want to continue using a reporting repository from an earlier version of Data Modeler, see the Reporting_Schema_Upgrade_readme.txt file in the datamodeler/reports directory.If you want to keep the database connection and schema but start with a new reporting repository, delete the existing repository (explained later in this topic) and then create the reporting repository. |
To create a reporting repository, follow these steps:
Click File, then Export, then To Reporting Schema.
In the Export to Reporting Schema dialog box, click the Add Connection (+) icon.
In the New/Update Database Connection dialog box, enter a name for the connection (for example, dm_reporting_repos_conn
), as well as the other information for the connection , including the user name and password for the database user associated with the reporting schema.
Optionally, click Test to test the connection. (If the test is not successful, correct any errors.)
Click OK to create the connection and to close the New/Update Database Connection dialog box.
Select (click) the connection name in the list of connections near the top of the dialog box.
Click OK to create the reporting repository in the schema associated with the selected connection, and to have the information about the selected models exported to that repository.
To delete an existing reporting repository, follow these steps:
Click File, then Export, then To Reporting Schema.
Select the connection for the schema associated with the reporting repository to be deleted.
In the Export to Reporting Schema dialog box, click the Maintenance tab.
Click Drop Repository, then confirm that you want to drop the reporting repository.
If you only want to deleted selected designs within the repository and not the entire repository, click Delete Designs and select the designs to be deleted.
For glossaries, you can perform the following operations using the Glossary tab of the Export to Reporting Schema dialog box:
Export Glossary: Enables you to specify a Data Modeler glossary file, to have its information exported to the reporting repository.
Delete Glossary: Enables you to select a glossary in the reporting repository, to have its information deleted from the repository.
Related Topics