How to Secure ALL_SOURCE using a Policy (DBMS_RLS) to Hide Body Implementations (Doc ID 333654.1)

Last updated on SEPTEMBER 08, 2023

Applies to:

PL/SQL - Version 9.2.0.1 and later
Information in this document applies to any platform.

Goal

Prevent users from using ALL_SOURCE to browse the source code of the implementation body of types and packages of which they have execute privilege but do not own. ALL_SOURCE must remain available to allow users to view the package and type specification.

Note: The wrap utility does allow the source code specification to be encrypted but the goal here is to make the body invisible so that no rows are returned when ALL_SOURCE is queried in that situation.

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How to Secure ALL_SOURCE using a Policy (DBMS_RLS) to Hide Body Implementations (Doc ID 333654.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!