This option is not the default because it causes all SQL statements to appear in plain text in the wrapped file. To enable the support for all SQL syntax, specify the option edebug=wrap_new_sql (with no dash). Some recent SQL syntax is not supported by the wrap utility by default. Wrapping a procedure helps to hide the algorithm and prevent reverse-engineering, but it is not a way to hide passwords or table names that you want to be secret. String literals, number literals, and names of variables, tables, and columns remain in plain text within the wrapped file. Normal importing and exporting-the Import/Export utility accepts wrapped files.

Strict dependency checking-invalidated program units are recompiled automatically.

Dynamic binding-external references are resolved at load time.

Dynamic loading-users need not shut down and re-link to add a new feature.

Platform independence-you need not deliver multiple versions of the same compilation unit.

The PL/SQL compiler recognizes and loads wrapped compilation units automatically. Wrapped code is as portable as source code.

Exposure of your algorithms to business competitors.

Misuse of your application by other developers.

This appendix discusses the following topics: Advantages of Wrapping PL/SQL Procedures Running the Wrap Utility Guidelines Advantages of Wrapping PL/SQL Proceduresīy hiding application internals, the Wrap Utility prevents You can use the Wrap Utility to deliver PL/SQL applications without exposing your source code. This appendix shows you how to run the Wrap Utility, a standalone programming utility that encrypts PL/SQL source code.

Rewrap.exe oracle