Creating and Customizing the Converted Model

After you capture a third-party database, the next step is to convert it, creating the converted model. The converted model is a representation of the structure of the destination database. SQL Developer creates the converted model using the information from the captured model.

By default, all procedures, functions, triggers, and views are copied to the converted model during translation and translated to Oracle PL/SQL. However, if translation fails for any of the objects, those objects appear in the converted model but their original SQL code remains unchanged. Objects that remain in their original SQL code will not be used when the generation scripts are created. Therefore, to have any such objects migrated, you must either fix the problem in the original SQL code before generating the script or edit the generated script to replace the original SQL code with valid PL/SQL code.

To convert a captured model to a converted model, right-click the appropriate node in the Captured Objects navigator and select Convert to Oracle, and specify or accept the defaults for data mappings.

The following topic describes how to modify the converted model, if this becomes necessary:

Related Topics

Migrating Third-Party Databases

Correcting Errors in the Converted Model

If error messages with the prefix Parse Exception are listed in the migration log, manual intervention is required to resolve the issues. To complete the converted model:

  1. Note the converted model schema object that failed.

  2. Select that schema object in the converted model.

  3. Copy the schema objects DDL and paste it into the translation scratch editor (displayed by clicking Migration, then Translation Scratch Editor).

  4. Inspect the properties on the schema object in the translation scratch editor for possible causes of the error.

  5. Modify a property of the schema object in the translation scratch editor.

    For example, you might comment out one line of a stored procedure.

  6. Translate using the appropriate translator.

  7. If the error appears again, repeat steps 2 to 6.

  8. If the error cannot be resolved in this way, it is best to modify the object manually in the converted model.