Skip Headers

# Troubleshooting Your Migration

Previous

Next

This section describes solutions for problems you may encounter during migration, including the following:

- Log Messages

- Unexpected Relational Multiplicity

Log Messages

As it operates, the TopLink migration tool logs all errors and diagnostic output to a log file named `oc4j_migration.log` in the output directory. If you use the TopLink migration tool from TopLink Workbench, see also the TopLink Workbench log file `oracle.toplink.workbench.log` located in your user home directory (for example, `C:\Documents and Settings\<``user-name``>`)

In addition to these warnings, the TopLink migration tool logs an error if it encounters a problem that prevents it from completing the migration. Table: TopLink Migration Tool Error Messages lists these problems and suggests possible solutions.

TopLink Migration Tool Error Messages

Error Message | Description
--- | ---

There is no `ejb-jar.xml` in the input file. You must provide the `ejb-jar.xml` in order for the migration process to work.

The `ejb-jar.xml` file is missing. The TopLink migration tool stops and copies the original input files into the target directory.

Verify that the `ejb-jar.xml` file is present in the specified EAR, JAR, or as a plain XML file. Empty the target directory and execute the TopLink migration tool again.

There is not an `orion-ejb-jar.xml` with native persistent metadata defined, no migration needed.

The `orion-ejb-jar.xml` file is missing. The TopLink migration tool stops and copies the original input files into the target directory.

Verify that the `orion-ejb-jar.xml` file is present in the specified EAR, JAR, or as a plain XML file. Empty the target directory and execute the TopLink migration tool again.

`toplink-ejb-jar.xml` is already defined in the archive, no migration needed. | A `toplink-ejb-jar.xml` file is already present in the target directory. The TopLink migration tool stops and copies the original input files into the target directory. Remove the `toplink-ejb-jar.xml` file from the target directory. Empty the target directory and execute the TopLink migration tool again.

Unexpected Relational Multiplicity

The TopLink migration tool retrieves relationship multiplicity from the `orion-ejb-jar.xml` file and not from the OC4J `ejb-jar.xml` file.

Thus, even though the OC4J `ejb-jar.xml` file defines a relationship to be one-to-many, if the `orion-ejb-jar.xml` file defines the same relationship as many-to-many, then the TopLink migration tool will migrate the relationship as many-to-many.