In JDeveloper you have two ways of creating and managing database connections. You can define database connections for an application (called an Application Resource connection) or for the IDE as a whole (called an IDE connection). You use the same dialog to define these, but their scope within JDeveloper is different.

When you first create a database connection, you choose the connection scope which you cannot subsequently change.

When you create a database connection, JDeveloper creates a node for the connection in the Databases window, and an additional node in either the Resources window or in the Application Resources panel of the Applications window depending on the scope of the connection.

Team level database connections are also available when JDeveloper is configured to work with teams.

In the Applications window and Databases window, you can expand the database connection node to view and work with database objects. In the Resources window, you can only work with a database connection after you have added it to the application.

A connections.xml file is included with JDeveloper deployments, and in the application it is in the folder .adf\META-INF. This file contains the connection information necessary for deployment and the runtime connection execution.

1. If necessary load database features by choosing Window > Database.
2. Open the Databases window by choosing Window > Database > Databases.
3. Right-click IDE Connections or the application, and choose New Connection to open the Create Database Connection dialog.

   Alternatively, from the main menu, choose File > New to open the New Gallery. In the Categories list, expand General and select Connections.

   Then, in the Items list, double-click Database Connection to open the Create Database Connection dialog.

   For more information at any time, press F1 or click Help from within the dialog.

4. Enter the appropriate connection information, then click Test Connection. You may have to briefly wait while JDeveloper connects to the database.

   If the test succeeds, a success message appears in the status text area. If the test does not succeed, an error appears. In this case, change any previously entered information as needed to correct the error, or check the error content to determine other possible sources of the error.

1. In the Create or Edit Database Connection dialog, click JDBC Parameters to open the JDBC Parameters dialog.
2. The dialog allows you to enter any property name/value pairs you require in order to create the connection. For more information at any time, press F1 or click Help from within the dialog.
3. To add a new parameter Click . A new row is displayed. Where the driver supports it there may be a list of possible parameters that you can select from, as shown in the figure.

   Figure 25-3 JDBC Parameters Dialog

   
   Description of "Figure 25-3 JDBC Parameters Dialog"

   Choose or enter the parameter you want to use and enter a default value for it.

4. Click OK on the dialog, then OK on the Database Connection dialog.

For some types of database connection, you can choose from more than one available driver. For example, if you choose DB2 UDB, as shown in the figure you can choose either of the available drivers.

Figure 25-4 Drivers Available

Description of "Figure 25-4 Drivers Available"

1. Choose Window > Database > Databases.
2. Expand IDE Connections or application, and select a database connection.
3. Right-click the connection and choose Properties to open the Edit Database Connection. For more information at any time, press F1 or click Help from within the Create Database Connection dialog.

You can import and export database connections, described below.

1. Choose Window > Database > Databases.
2. Expand IDE Connections or application, and select a database connection.
3. Right-click the connection and choose Disconnect.

1. Choose Window > Database > Databases.
2. Expand IDE Connections or application, and select a database connection to delete.
3. Right-click the connection and choose Delete.
4. In the confirmation dialog, click Yes.

1. Choose Tools > Preferences.
2. In the Preferences dialog, select JDBC Driver Options.
3. The list of third-party JDBC drivers currently registered with JDeveloper is displayed. To add a new entry to the list, click New.

   A new entry appears in the list and in the Driver Class field, with a default driver class name.

4. In the Driver Class field, alter the new entry to reflect its fully qualified class name.

   Make sure that the correct entry is still selected in the Registered JDBC Drivers list.

5. Select a library to associate the driver with. You can browse to an existing library, or enter the fully qualified path to the library. The classpath for the library is displayed in Classpath.

   Be sure to include this library in any project that uses the third-party driver.

6. Click OK.

   The driver will now appear in the list of available third-party JDBC drivers both in this dialog (after you return to it) and in the Create Database Connection dialog.

1. Choose Tools > Manage Libraries.
2. In the Manage Libraries dialog, select the Libraries tab, then select the User node, and click New.
3. In the Create Library dialog, enter a library name, select the Class Path node, and click Add Entry. In the Select Path Entry dialog, browse to the location of the drivers for the database you are connecting to. Select the driver files, and click Select.
4. In a similar way, in the Create Library dialog, enter a library name, select the Source Path node, and click Add Entry. In the Select Path Entry dialog, browse to the location of the drivers for the database you are connecting to. Select the driver files, and click Select.
5. In the Create Library dialog, click OK, and in the Manage Libraries dialog, click OK.

When you create connections using Oracle's JDBC/OCI drivers, be aware of the following platform-specific requirements:

• You must have the required native libraries (.dll files on Windows, and .so/.sl files on UNIX).

  With the Oracle Type 2 driver (JDBC/OCI), the version of the JDBC driver must match the version of the Oracle home. For example, the Oracle JDBC Driver version 11 requires that Oracle home contain version 11 of ocijdbc11.dll, as well as the Oracle Network software and Required Support Files.

  You can download drivers from the JDBC Driver Downloads page at http://www.oracle.com/technetwork/database/features/jdbc/index-091264.html.

  If you are connecting to a local database which is a different version from the JDBC driver you are using, then you must install the Oracle client software into a separate Oracle home, and connect via the Oracle Net Listener.

• You must place the ORACLE_HOME directory in which the client-side file for the required native libraries resides into a directory listed in your PATH environment variable.

  • On Windows: In your PATH environment variable list the %ORACLE_HOME%\bin directory in which the client-side DLL file resides. If you have multiple Oracle homes installed on your machine, use the Oracle home Switch utility to choose the correct Oracle home.

  • On UNIX: List the {ORACLE_HOME}/lib directory in which the client-side .so/.sl file resides in your PATH environment variable.

• If your Oracle home for the OCI driver is not the same as the Oracle home in which JDeveloper is installed, you must set the ORACLE_HOME environment variable.

• If your Oracle home for the OCI driver is not the same as the Oracle home in which JDeveloper is installed and you have no other OCI drivers listed in java.library.path, you can edit {$ORACLE_HOME}/jdeveloper/jdev/bin/jdev.conf with a line similar to the following, replacing the path shown with the full path to your Oracle home:

  On Windows: AddNativeCodePath C:/ORACLE/ORAnn/BIN

  On UNIX: AddNativeCodePath /u01/app/oracle/product/n.n.n/lib

  AddNativeCodePath adds to java.library.path the directory name in which the Java VM searches for shared libraries.

  Note:

  Because AddNativeCodePath only appends the directory to the path, if you have an OCI driver path already in the PATH environment variable, set ORACLE_HOME instead of editing PATH with AddNativeCodePath.

You can browse online databases and offline database objects.

1. Choose View > Database > Databases window.
2. Expand a connection to view the schemas available.
3. Expand a schema to view all the object types visible.
4. If necessary, apply a filter at the connection, schema, or database object type level.

1. In the Applications window, expand the project containing your offline schemas.
2. Expand Offline Database Sources and then expand the database and schema you want to browse.

1. Choose Window > Database > Databases.
2. Expand IDE Connections or application, and select a database connection.
3. Expand the connection if it has not yet been loaded. Filtering is not available until the connection has been loaded (once per connection per JDeveloper session). Select a connection, schema within a connection, or node within a schema:
4. If a filter is currently applied to the selection, a filter icon appears on the node of the selected object, and (filtered) appears next to the node name, as shown in the figure.

   Figure 25-5 Filtered Objects in Databases Window

   
   Description of "Figure 25-5 Filtered Objects in Databases Window"

   With the object still selected, click the Apply Filter button in the Databases window toolbar and a dialog appears, showing the current selection, if any. From this dialog, you can change the filter currently applied.

1. Choose Window > Database > Databases.
2. Expand IDE Connections or application.
3. Select the connection, schema within a connection, or node within a schema, then perform either of these actions:

   • Right-click your selection and choose Apply Filter.

   • In the Databases window toolbar, click the Apply Filter button in the Databases window toolbar.

4. A filter dialog appears, appropriate to the object you selected. For connections and schema, a selection box appears. For other objects, type in the text (case-sensitive) which JDeveloper matches to object names in the selected node. You can use the wildcard character %.
5. Click OK. Notice that the list of objects is now filtered to display only those names that match the criteria you selected.

1. Open the table in the Database Object Viewer by selecting it in the Databases window and double-clicking it. Alternatively, you can right-click the table and choose Open.
2. Select the tab that contains the information you are interested in, for example, Columns. For more information at any time, press F1 or click Help from within the Database Object Viewer.

1. Display the table in the Database Object Viewer by double-clicking it in the Databases window.
2. Click the Data tab to display the contents of the table.
3. Position the cursor in the cell you want to change and type the new value.

   • To add a new record, click the Insert Row button.

   • To delete one or more records, select them and click the Delete Selected Row(s) button.

4. When you have finished, either:

   • Click the Commit Changes button to commit your changes to the database.

   • Click the Rollback Changes button to rollback your changes.

1. From the main menu, choose Window > Database > Find DB Object to open the Find Database Object Window.

   For more information at any time, press F1 or click Help from within the window.

2. Select the connection name from the Connection list.
3. Enter search terms in the Name field. You can use the wildcard % to return a number of matching objects. For example, enter EM% to return all objects with names starting with EM.
4. If necessary, click More to enter more search criteria.
5. Click Lookup. The results are returned in the Search window. To view or edit one of the objects (or the parent object that contains the specified object), double-click or right-click its name in the results display.

When you create a database connection using the Create Database Connection dialog, the new connection is created and a node representing the connection is displayed in the:

• Databases window.

• Applications window.

• Resources window.

You can connect to and work with Oracle databases. For information about the specific versions that are supported, see "JDeveloper Certification Information" at http://www.oracle.com/technetwork/developer-tools/jdev/documentation/index.html.

1. Create a library containing the JDBC drivers.
2. Create a database connection.
3. In the Create Database Connection dialog, enter the appropriate values for the database. For more information, refer to the help topic for the database you are connecting to.
4. Finally, you must configure your projects to use the correct data types.

Create connections in JDeveloper to databases.

JDeveloper connects to an Oracle Database Cloud Service instance using two types of connection:

• Database Connection: This connection is made using the Service Home URL (identified in the "Welcome to Oracle Cloud" email). This URL connects to Oracle Application Express and you can browse database objects and deployments on your Oracle Database Cloud Service instance from a node in the Databases window. The connection is not validated until you connect to the Oracle Database Cloud Service instance, when you are prompted to provide a password.

• Secure FTP connection: The Secure FTP hostname and SFTP user identified in the "Welcome to Oracle Cloud" email are used in this connection to upload the deployment ZIP file to your Oracle Database Cloud Service instance using SFTP. At the Oracle Database Cloud Service end, there is a background job which runs to download these files and put them onto the Oracle Database Cloud Service instance.

  Once you have entered the Secure FTP hostname and user, either in the Create or Edit Cloud Connection Dialog or the Deploy Objects to Cloud Dialog, the information is saved and will be present the next time you deploy objects to your Oracle Database Cloud Service instance.

  If you have just signed up for Oracle Database Cloud Service, there are some steps you have to carry out before trying to create a connection from JDeveloper. For example, the Identity Domain Administrator has to create new passwords for the Service Home and for the Secure FTP Site. The information you need is in the "Welcome to Oracle Cloud" email.

  Also, you have to create users who can create database connections to Oracle Database Cloud Service instances. See About Database Cloud Service Roles and Users.

The Cart is a convenient tool for collecting Oracle Database objects from one or more database connections, and deploying, exporting, comparing, or copying those objects. You can put objects into one or more carts, each with its own tab. When the Cart window is opened, it contains an empty cart, although you can create new carts and open previously saved carts in new or existing cart tab.

Objects in the Cart are not automatically synchronized with database activity; to update the contents of the cart with the current state of the database, click the Refresh icon. If an object does not exist after a refresh, the object is disabled in the Cart and is underlined to indicate the error

You can put database objects into a cart tab in several ways:

• Drag and drop objects from the Databases window into the Cart window.

• Select one or more objects in the Databases window, right-click, and select Add to Cart.

• Open a previously saved Cart XML file.

• Add scripts By using the Scripts icon drop-down (Add Initial Script, Add Final Script). (If you use a Cart tool that does not support scripts, they are ignored.)

When you choose the SQL*Loader option in the Data Import Wizard, JDeveloper creates the following files in the same location as the import file containing the data: table.ctl, which contains information about the file containing the data and the table into which it can be imported. table.bat and table.sh, to run the import. See see SQL*Loader Concepts.

You can import data into an external table, which is a flat file in which you can query data as though it were an Oracle table.

When you choose the External Table option, JDeveloper creates the SQL and displays it in the SQL Worksheet where you can examine it and make any necessary changes before running the script. See Using External Tables to Move Data.

1. From the main menu, choose Window > Database > Databases to open the Databases window.
2. If necessary, create a connection to the database.
3. Expand the node for the database connection, the schema, Tables, and select the table node you want to import data to.
4. Right-click and choose Import Data and in the Open dialog enter or browse to the location of the file.

   Click OK to launch the Data Import Wizard.

   For more information at any time, press F1 or click Help from within the wizard.

1. From the main menu, choose Window > Database > Databases to open the Databases window.
2. If necessary, create a connection to the database.
3. Expand the node for the database connection and the schema. Right-click the Tables node and choose Import Data.
4. In the Open dialog enter or browse to the location of the file. Click OK to launch the Data Import Wizard.

   For more information at any time, press F1 or click Help from within the wizard.

5. On the Column Definition page of the Data Import wizard, enter the name of the new table.

1. From the main menu, choose Window > Database > Databases to open the Databases window.
2. If necessary, create a connection to the database.
3. Expand the node for the database connection, the schema, Tables, and select the table node you want to import data to.
4. Right-click and choose Import Data and in the Open dialog enter or browse to the location of the file.

   Click OK to launch the Data Import Wizard.

   For more information at any time, press F1 or click Help from within the wizard.

5. On the Data Preview page of the Data Import wizard, choose SQL*Loader Table.
6. On the Options page of the Data Import wizard, choose the options for the generated file.
7. When you complete the Data Import wizard, the SQL*Loader control file called table.ctl is created in the same location as the data file, along with a table.bat and table.sh files which allow you to run it. If you selected Send to worksheet on the Finish page of the Data Import wizard, the SQL defining the table is displayed in the SQL Worksheet.

1. If necessary, create a connection to the database.
2. Expand the node for the database connection and the schema. Right-click the Tables node and choose Import Data and in the Open dialog enter or browse to the location of the file.
3. Click OK to launch the Data Import Wizard.

   For more information at any time, press F1 or click Help from within the wizard.

4. On the Data Preview page of the Data Import wizard, choose External Table.
5. On the Options page of the Data Import wizard, choose the options for the generated file. When you complete the Data Import wizard, the SQL is displayed in the SQL Worksheet, where you can examine it and make any changes. When you are satisfied, right-click in the Worksheet, and choose Run in SQL*Plus.

You can export data from tables in a database through a database connection.

The data can be saved to a file or to the clipboard. The following formats are supported:

• csv, to create a file containing comma-separated values including a header row for column identifiers.

  Note:

  You can choose a different delimiter.
• fixed, to create a file where records are the same byte length.
• html, to create an HTML file containing a table with the data. insert, to create a file containing SQL INSERT statements.
• loader, to create a SQL*Loader control file. See SQL*Loader Concepts.
• text, to create a text file.
• ttbulkcp, to create a data files to be used with the TimesTen ttbulkcp command line utility. For more information, see the TimesTen In-Memory Database page.
• xls, to create a Microsoft Excel .xls file. The file will contain two worksheets, Export Worksheet, which contains the data, and SQL which contains the SQL statement used to export the data.
• xml, to create a file containing XML tags and data.

In the Export Data dialog, you can limit the data to be exported by selecting only some columns, and by entering a WHERE clause.

You can also export data from a database using the Export Database wizard.

1. From the main menu, choose Window > Database > Databases to open the Databases window.
2. If necessary, create a connection to the database.
3. Expand the node for the database connection, the schema, Tables, and select the table node you want to export data from.
4. Right-click and choose Export Data to open the Export Data dialog.

   For more information at any time, press F1 or click Help from within the wizard.

1. From the main menu, choose Tools > Database > Database Copy to open the New Copy wizard.

   For more information at any time, press F1 or click Help from within the wizard.

1. From the main menu, choose Tools > Database > Database Diff to open the Diff wizard.

   For more information at any time, press F1 or click Help from within the wizard.

1. From the main menu, choose Tools > Database > Database Export to open the Export Database wizard.

   For more information at any time, press F1 or click Help from within the wizard.

JDeveloper provides many reports about a database and its objects. You can also create your own user-defined database reports.

For some reports, you are prompted for bind variables before the report is generated. These bind variables enable you to further restrict the output. The default value for all bind variables is null, which implies no further restrictions.

The Database Reports window allows you to run reports which query the database for the latest information. The time required to display specific reports will vary, and may be affected by the number and complexity of objects involved, and by the speed of the network connection to the database.

There are a number of predefined reports about the database and its objects.

You can also create your own user-defined reports.

You can examine the underlying SQL for a report, for example, to help you create your own report.

Database reports are organized in folders, and reports and folders can be exported.

You can share reports by exporting them.

The person who wants to share the report then adds it to their instance of JDeveloper using the Preferences dialog. Reports that have been exported can be imported into folders under the User Defined Reports node.

This section describes the pre-defined reports available under the Data Dictionary Reports node in the Database Reports window.

The reports are grouped into categories, with one or more different reports available in that category.

• About Your Database Reports

  These reports list release information about the database associated with the connection. The reports include Version Banner (database settings) and National Language Support Parameters (NLS_xxx parameter values for globalization support).

• All Objects Reports

  These reports list information about all objects accessible to the user associated with the specified database connection, not just objects owned by the user.

  • All Objects: For each object, lists the owner, name, type (table, view, index, and so on), status (valid or invalid), the date it was created, and the date when the last data definition language (DDL) operation was performed on it. The Last DDL date can help you to find if any changes to the object definitions have been made on or after a specific time.

  • Collection Types: Lists information about each collection type. The information includes the type owner, element type name and owner, and type-dependent specific information.

  • Dependencies: For each object with references to it, lists information about references to (uses of) that object.

  • Invalid Objects: Lists all objects that have a status of invalid.

  • Object Count by Type: For each type of object associated with a specific owner, lists the number of objects. This report might help you to identify users that have created an especially large number of objects, particularly objects of a specific type.

  • Public Database Links: Lists all public database links.

  • Public Synonyms: Lists all public synonyms.

• Application Express Reports

  These reports list information about Oracle Application Express 3.0.1 (or later) applications, pages, schemas, UI defaults, and workspaces. If you select a connection for a schema that owns any Oracle Application Express 3.0.1 (or later) applications, the Application Express reports list information about applications, pages, schemas, UI defaults, and workspaces. For information, see Application Express Administration Guide.

• ASH and AWR Reports

  These reports list information provided by the Active Session History (ASH) and Automated Workload Repository (AWR) features.

• Database Administration Reports

  These reports list usage information about system resources. This information can help you to manage storage, user accounts, and sessions efficiently. (The user for the database connection must have the DBA role to see most Database Administration reports.)

  • All Tables: Contains the reports that are also grouped under Table reports, including Quality Assurance reports.

  • Cursors: Provide information about cursors, including cursors by session (including open cursors and cursor details.

  • Database Parameters: Provide information about all database parameters or only those parameters that are not set to their default values.

  • Locks: Provide information about locks, including the user associated with each.

  • Sessions: Provide information about sessions, selected and ordered by various criteria.

  • Storage: Provide usage and allocation information for tablespaces and data files.

  • Top SQL: Provide information about SQL statements, selected and ordered by various criteria. This information might help you to identify SQL statements that are being executed more often than expected or that are taking more time than expected.

  • Users: Provide information about database users, selected and ordered by various criteria. For example, you can find out which users were created most recently, which user accounts have expired, and which users use object types and how many objects each owns.

• Data Dictionary Reports

  These reports list information about the data dictionary views that are accessible in the database. Examples of data dictionary views are ALL_OBJECTS and USER_TABLES.

  • Dictionary View Columns: For each Oracle data dictionary view, lists information about the columns in the view.

  • Dictionary Views: Lists each Oracle data dictionary view and (in most cases) a comment describing its contents or purpose.

• Jobs Reports

  These reports list information about jobs running on the database.

  • All Jobs: Lists information about all jobs running on the database. The information includes the start time of its last run, current run, and next scheduled run.

  • DBA Jobs: Lists information about each job for which a DBA user is associated with the database connection. The information includes the start time of its last run, current run, and next scheduled run.

  • Your Jobs: Lists information about each job for which the user associated with the database connection is the log user, privilege user, or schema user. The information includes the start time of its last run, current run, and next scheduled run.

• PLSQL Reports

  These reports list information about your PL/SQL objects and allow you to search the source of those objects.

  • Program Unit Arguments: For each argument (parameter) in a program unit, lists the program unit name, the argument position (1, 2, 3, and so on), the argument name, and whether the argument is input-only (In), output-only (Out), or both input and output (In/Out).

  • Search Source Code: For each PL/SQL object, lists the source code for each line, and allows the source to be searched for occurrences of the specified variable.

  • Unit Line Counts: For each PL/SQL object, lists the number of source code lines. This information can help you to identify complex objects (for example, to identify code that may need to be simplified or divided into several objects).

• Security Reports

  These reports list information about users that have been granted privileges, and in some cases about the users that granted the privileges. This information can help you (or the database administrator if you are not a DBA) to understand possible security issues and vulnerabilities, and to decide on the appropriate action to take (for example, revoking certain privileges from users that do not need those privileges).

  • Auditing: Lists information about audit policies.

  • Encryption: Lists information about encrypted columns.

  • Grants and Privileges: Includes the following reports:

    • Column Privileges: For each privilege granted on a specific column in a specific table, lists the user that granted the privilege, the user to which the privilege was granted, the table, the privilege, and whether the user to which the privilege was granted can grant that privilege to other users.

    • Object Grants: For each privilege granted on a specific table, lists the user that granted the privilege, the user to which the privilege was granted, the table, the privilege, and whether the user to which the privilege was granted can grant that privilege to other users.

    • Role Privileges: For each granted role, lists the user to which the role was granted, the role, whether the role was granted with the ADMIN option, and whether the role is designated as a default role for the user.

    • System Privileges: For each privilege granted to the user associated with the database connection, lists the privilege and whether it was granted with the ADMIN option.

  • Policies: Lists information about policies.

  • Public Grants: Lists information about privileges granted to the PUBLIC role.

• Streams Reports

  These reports list information about stream rules.

  • All Stream Rules: Lists information about all stream rules. The information includes stream type and name, rule set owner and name, rule owner and name, rule set type, streams rule type, and subsetting operation.

  • Your Stream Rules: Lists information about each stream rule for which the user associated with the database connection is the rule owner or rule set owner. The information includes stream type and name, rule set owner and name, rule owner and name, rule set type, streams rule type, and subsetting operation.

• Table Reports

  These reports list information about tables owned by the user associated with the specified connection. This information is not specifically designed to identify problem areas; however, depending on your resources and requirements, some of the information might indicate things that you should monitor or address.

  For table reports, the owner is the user associated with the database connection.

  • Columns: For each table, lists each column, its data type, and whether it can contain a null value. Also includes:

  • Data type Occurrences: For each table owner, lists each data type and how many times it is used.

  • Comments for tables and columns: For each table and for each column in each table, lists the descriptive comments (if any) associated with it. Also includes a report of tables without comments. If database developers use the COMMENT statement when creating or modifying tables, this report can provide useful information about the purposes of tables and columns

  • Constraints: Includes the following reports related to constraints:

  • All Constraints: For each table, lists each associated constraint, including its type (unique constraint, check constraint, primary key, foreign key) and status (enabled or disabled).

  • Check Constraints: For each check constraint, lists information that includes the owner, the table name, the constraint name, the constraint status (enabled or disabled), and the constraint specification.

  • Enabled Constraints and Disabled Constraints: For each constraint with a status of enabled or disabled, lists the table name, constraint name, constraint type (unique constraint, check constraint, primary key, foreign key), and status. A disabled constraint is not enforced when rows are added or modified; to have a disabled constraint enforced, you must edit the table and set the status of the constraint to Enabled (see the appropriate tabs for the Create/Edit Table (with advanced options) dialog box).

  • Foreign Key Constraints: For each foreign key constraint, lists information that includes the owner, the table name, the constraint name, the column that the constraint is against, the table that the constraint references, and the constraint in the table that is referenced.

  • Primary Key Constraints: For primary key constraint, lists information that includes the owner, the table name, the constraint name, the constraint status (enabled or disabled), and the column name.

  • Unique Constraints: For each unique constraint, lists information that includes the owner, the table name, the constraint name, the constraint status (enabled or disabled), and the column name.

  • Indexes: Includes information about all indexes, indexes by status, indexes by type, and unused indexes.

  • Organization: Specialized reports list information about partitioned tables, clustered tables, and index-organized tables.

  • Quality Assurance: (See Quality Assurance reports.)

  • Statistics: For each table, lists statistical information, including when it was last analyzed, the total number of rows, the average row length, and the table type. In addition, specialized reports order the results by most rows and largest average row length.

  • Storage: Lists information about the table count by tablespace and the tables in each tablespace.

  • Triggers: Lists information about all triggers, disabled triggers, and enabled triggers.

  • User Synonyms: Displays information about either all user synonyms or those user synonyms containing the string that you specify in the Enter Bind Variables dialog box (deselect Null in that box to enter a string).

  • User Tables: Displays information about either all tables or those tables containing the string that you specify in the Enter Bind Variables dialog box (deselect Null in that box to enter a string).

  • Quality Assurance reports: These are table reports that identify conditions that are not technically errors, but that usually indicate flaws in the database design. These flaws can result in various problems, such as logic errors and the need for additional application coding to work around the errors, as well as poor performance with queries at run time.

  • Tables without Primary Keys: Lists tables that do not have a primary key defined. A primary key is a column (or set of columns) that uniquely identifies each row in the table. Although tables are not required to have a primary key, it is strongly recommended that you create or designate a primary key for each table. Primary key columns are indexed, which enhances performance with queries, and they are required to be unique and not null, providing some automatic validation of input data. Primary keys can also be used with foreign keys to provide referential integrity.

  • Tables without Indexes: Lists tables that do not have any indexes. If a column in a table has an index defined on it, queries that use the column are usually much faster and more efficient than if there is no index on the column, especially if there are many rows in the table and many different data values in the column.

  • Tables with Unindexed Foreign Keys: Lists any foreign keys that do not have an associated index. A foreign key is a column (or set of columns) that references a primary key: that is, each value in the foreign key must match a value in its associated primary key. Foreign key columns are often joined in queries, and an index usually improves performance significantly for queries that use a column. If an unindexed foreign key is used in queries, you may be able to improve run-time performance by creating an index on that foreign key.

• XML Reports

  These reports list information about XML objects.

  • XML Schemas: For each user that owns any XML objects, lists information about each object, including the schema URL of the XSD file containing the schema definition.

If you get the following ORA-29552: verification warning: java.lang.UnsupportedClassVersionError when deploying Java to the database you need to change the version of the JDK used for that project to a version compatible with that used by the database.

For information about the JDK, see "JDeveloper Certification Information" at http://www.oracle.com/technetwork/developer-tools/jdev/documentation/index.html.

For information about the JDK used by the database, consult your database documentation.

For information about changing the Java SE on a project by project basis, see the section on setting the target Java SE in How to Set Properties for Individual Projects.

You can download previous releases of Java SE from http://www.oracle.com/technetwork/java/javase/downloads/index.html.