Caching is defined in TDV on specific resources, you must have access to a resource to create a cache for it. The user who owns the resource being cached is the user identity that cache refresh and clear operations are run with.

TDV caching typically requires the creation of objects on the data source that is acting as the cache target. To create and delete the data and objects necessary for caching with TDV you must have the necessary permissions set up for you in the cache target. Performing a cache refresh or clear requires the READ, SELECT, INSERT, UPDATE, and DELETE privileges on the status table, tracking table, and the data tables. For example, if you use an Oracle database as your caching target, the TDV user that is defining the cache must have privileges on the Oracle database to READ, SELECT, INSERT, UPDATE, and DELETE data and objects directly in the database. Those privileges can be granted by explicit assignment, or by membership in a group with those privileges (implicit assignment).

For someone to use the view or procedure that is being cached to the cache target, they must also have privileges granted to access the cache status and data tables. For someone to read from the cache, they must be granted the SELECT privilege on these tables and READ privileges on folders above these tables.

Privileges are managed automatically when using the Automatic mode of caching.