A script-enabled browser is required for this page to function properly.

PL/SQL conversion utility: How does it work?

You can use the conversion utility interactively or in batch mode. In either case, you control whether or not the utility actually updates your code. Interactive mode provides a greater degree of flexibility, as you can let the utility make some changes and make others manually. In batch mode, the utility either makes all of the conversions it can or none of them. Regardless of whether the conversion occurs in interactive or batch mode, a summary of the conversion process is written to a log file called module.plg.

Note: Before deciding which mode to use, try converting a few modules of each type interactively.   That will give you an idea of the kinds of issues you’re facing in each type of module, and may help you decide how to proceed.   For example, you might discover that your forms require the close monitoring that interactive mode provides, while your reports and PL/SQL libraries can be safely converted in batch mode.

While the conversion utility can upgrade your code to resolve several V1 or V2 incompatibilities, there are some situations it can’t address. These result in compiler errors, which are listed in the PL/SQL V1 Conversion Summary dialog box (interactive mode) or in the log file so you can address them manually.

After the conversion utility converts and saves an application—even if you choose to ignore all suggested conversions—the utility is never again invoked for that application. This prevents the utility from overwriting any changes you may have made manually.

See also

About the PL/SQL conversion utility

What does it convert?

What can it not convert?