Creating the PL/SQL policy function alone doesn't activate Virtual Private Database protection. The function must be associated with the database object that requires protection. Oracle uses the DBMS_RLS.ADD_POLICY procedure to attach the VPD policy and its policy function to a table, view, or synonym. Once associated, Oracle Database automatically incorporates the policy predicate whenever relevant SQL accesses that object.

The implementation should then be tested directly at the database layer , using a SQL client such as Oracle SQL Developer. Testing with different application or proxy-user contexts confirms that the predicate returns the intended row subsets before Publisher reporting depends on the security configuration.

Catalog roles don't substitute for VPD because catalog permissions protect report objects rather than rows inside database tables. Creating separate reports for individual users would duplicate content and fail to implement centralized row security. Proxy authentication is often useful with Publisher because it preserves individual identity for database-side security enforcement, so disabling it isn't the appropriate completion step. A database restart isn't normally required after attaching a VPD policy.

Thus, the correct database-side actions are apply the policy to the target table and validate its behavior using a SQL tool .

Reference Topic: Managing and Securing Oracle Analytics Publisher — Implementing and Validating VPD Policies

===============