A.A package definition must have a specification and body.

B.Package specifications can be compiled without their bodies.

C.Variables and cursors defined in a package specification are visible to all subprograms in the same schema that has the package.

D.Modifications to a packaged procedure's body automatically cause recompilation of subprograms that invoke the procedure.

E.Standalone subprograms that reference a package can be compiled only after both the package specification and body are compiled.

A.Anonymous blocks cannot use packaged variables.

B.Anonymous blocks must always start with the Declare keyword.

C.Named subprograms are stored in the database server.

D.FUNCTION subprograms must be called and passed through one or more parameters.

E.Named subprograms cannot be called from other packages.

F.PROCEDURE subprograms can accept parameters.

G.A FUNCTION subprogram must return one or more values.

A.Internally defined exceptions can be handled only by the OTHERS exception handler.

B.Predefined exceptions are globally declared in the standard package.

C.Only predefined exceptions and user-defined exceptions can have a user-declared name associated with them.

D.User-defined exceptions can be defined in the declarative part of any PL/SQL anonymous block, subprogram, or package.

E.All declared exceptions are raised implicitly by the runtime system.

A.Subprograms are cached by default and shared among users, thereby reducing memory requirements.

B.Host variables can be referenced inside any PL/SQL subprogram.

C.Reuse of parsed PL/SQL code from the shared SQL area reduces parsing overhead.

D.A PL/SQL procedure can invoke an external code block written in a different programming language.

E.A subprogram's session state is retained even if any of the session's instantiated subprograms are invalidated and revalidated.

F.Users granted execute privilege on a procedure compiled with definer's rights require grants to access objects belonging to the definer that are referenced in the procedure.

G.Results of a subprogram can be cached in the SGA such that sessions connected to the same instance can reuse these results when available.

A.line 3

B.line 7

C.line 4

D.line 6

E.line 5

F.line 2