|Oracle9i SQL Reference
Release 2 (9.2)
Part Number A96540-01
SQL Statements: ALTER CLUSTER to ALTER SEQUENCE, 16 of 21
PROCEDURE statement to explicitly recompile a standalone stored procedure. Explicit recompilation eliminates the need for implicit run-time recompilation and prevents associated run-time compilation errors and performance overhead.
To recompile a procedure that is part of a package, recompile the entire package using the
PACKAGE statement (see ALTER PACKAGE).
This statement does not change the declaration or definition of an existing procedure. To redeclare or redefine a procedure, use the
PROCEDURE statement is quite similar to the
The procedure must be in your own schema or you must have
PROCEDURE system privilege.
Specify the schema containing the procedure. If you omit
schema, Oracle assumes the procedure is in your own schema.
Specify the name of the procedure to be recompiled.
COMPILE to recompile the procedure. The
COMPILE keyword is required. Oracle recompiles the procedure regardless of whether it is valid or invalid.
During recompilation, Oracle drops all persistent compiler switch settings, retrieves them again from the session, and stores them at the end of compilation. To avoid this process, specify the
DEBUG to instruct the PL/SQL compiler to generate and store the code for use by the PL/SQL debugger.
Oracle9i Application Developer's Guide - Fundamentals for information on debugging procedures
SETTINGS to prevent Oracle from dropping and reacquiring compiler switch settings. With this clause, Oracle preserves the existing settings and uses them for the recompilation.
If you specify both
SETTINGS, Oracle sets the persistently stored value of the
PLSQL_COMPILER_FLAGS parameter to
DEBUG. No other compiler switch values are changed.
PL/SQL User's Guide and Reference and Oracle9i Application Developer's Guide - Fundamentals for more information on the interaction of the
To explicitly recompile the procedure
remove_emp owned by the user
hr, issue the following statement:
If Oracle encounters no compilation errors while recompiling
credit becomes valid. Oracle can subsequently execute it without recompiling it at run time. If recompiling
credit results in compilation errors, Oracle returns an error and
credit remains invalid.
Oracle also invalidates all dependent objects. These objects include any procedures, functions, and package bodies that call
credit. If you subsequently reference one of these objects without first explicitly recompiling it, Oracle recompiles it implicitly at run time.