You may receive an error if the source database includes datatypes that are not supported by the JDBC driver.

To resolve the error, perform one of the following tasks:

Convert the table to a view. Use SQL functions, such as CONVERT, to convert the table to a view. Translate the column datatype to a generic datatype such as CHAR, VARCHAR, or NUMBER. Then, mine the view.
Use a custom JDBC driver to mine the data. When you mine the database, use the CUSTOM_JDBC option. If you use a custom JDBC driver, you must use the standalone version of the Enterprise Data Manager. You cannot assign custom jar files for the web-based Enterprise Data Manager. Copy the jar files to the local machine from where you run the mining job.

The Enterprise Data Manager is a client application that is launched using JNLP protocol. Every client application has memory limitations. The Enterprise Data Manager may run out of memory when you use the client to mine data, export metadata, or import metadata.

You may receive a

java.lang.OutOfMemoryException

error when you mine large numbers of tables. Or, when you import or export a metadata for an application version that includes a large number of tables and constraints. When the Enterprise Data Manager is out of memory, the job does not progress in the status window. Java can use up to 2 gigabytes of RAM, which is usually not enough for large applications.

To resolve this error, run the jobs in the background. When you run the job in the background, the job runs on the Data Archive server instead of on the Enterprise Data Manager client machine.

The reason you cannot see a table in the Import Metadata from Database Wizard might be because the table contains a special character in the table name.

You cannot import metadata if the table name contains one of the following special characters:

~

,

!

,

@

,

#

,

$

,

?

,

%

,

^

,

&

,

*

,

_

,

+

,

-

, and

=

.