Using Trace Files to Troubleshoot Oracle Data Redaction Policies

B Using Trace Files to Troubleshoot Oracle Data Redaction Policies

Trace files for Oracle Data Redaction can be generated at either the system level or the session level.

You must set the tracing to high. There is no low level tracing for Oracle Data Redaction.

Connect to the PDB as a user who has the ALTER SYSTEM or ALTER SESSION privilege.
Enable tracing.
- At the system level, for all sessions:
```
ALTER SYSTEM SET events 'TRACE[RADM] disk=high';
```
- At the session level, for the current session:
```
ALTER SESSION SET events 'TRACE[RADM] disk=high';
```
To find problems with queries involving redacted columns, include /* KZDMPRQB_DUMP */ in the query. For example:
```
SELECT /* KZDMPRQB_DUMP */ redacted_column FROM table_with_redaction_policy;
```
Search for KCCF2MASK and KCCF2MASKDEP in the dump. The subsequent part of the dump files gives Oracle Redaction-specific insights.
To disable tracing:
- At the system level, for all sessions:
```
ALTER SYSTEM SET EVENTS 'TRACE[RADM] OFF';
```
- At the session level, for the current session:
```
ALTER SESSION SET EVENTS 'TRACE[RADM] OFF';
```