Attend the free webinar by the Oracle ACE Director Martin Widlake and learn how Oracle works under the hood. About the Webinar:
Despite the complexity and capability of the Oracle database, at it's heart there are a relatively small number of key activities and processes. If you understand them, you will get a lot more out of the database and advanced topics make a lot more sense. In this presentation I explain the key things the database does and how they work together. If you know what a SELECT statement is, you will understand this talk. And by the end of it, you will know some things that even many experienced developers and DBAs don't know. In this webinar, you will learn: The two ways Oracle reads data from disc and how it writes it back.That REDO is actually the most important part of the database. What happens when you COMMIT.Why Oracle data blocks are key to the buffer cache.What a "Consistent Get" really is.Why indexes are so powerful and what "balanced B…
Wrapping process makes PL/SQL source code unreadable. Developers can wrap package specifications, package bodies, functions, procedures, type specifications and type bodies. Unfortunately triggers cannot be wrapped. To wrap the trigger code you need to place your source code to a package or procedure and call it from the trigger.
There are two ways to wrap PL/SQL source code.
1. Wrapping PL/SQL source code with wrap utility
Wrap utility takes two parameters. First one (iname) is the PL/SQL source code file and the second one (oname) is the output file that will hold the wrapped code.
wrap iname=example_input_file.sql oname=example_output_file.plb
This is an easy way to wrap source code because you do not need to handle DDLs bigger than 32767 bytes. But this way, you need to save DDLs into different files and execute the wrap command frmo the command prompt for each file.
2. Wrapping PL/SQL source code with DBMSL_DDL package
The DBMS_DDL package contains an overloaded wrap API to wrap PL…