The sessions used by apply APPLY can access various information pertaining to the data being applied. See also Triggers.
...
On 10.2.0.5 and 11.2.0.2 and later, the session is marked as an apply APPLY session, so Oracle does not fire triggers that have trigger firing property set.
...
- is_dbreplicate_session: set to true in apply APPLY session.
xid, sid, serial, cuser, luser, cliinfo, osuser, machine, osterm, osproc, osprog, scn, datetime: audit information from the source. Identical to values described in CDC/Audit for realReal-time Time Data Warehousing. By default, this is set on transaction start and before execution of PL/SQL conflict handler.
- conflict_sqlerrm: error message of last current conflict. Updated before execution of PL/SQL conflict handler.
...
Only flag to identify that the sessoin session was spawned by apply APPLY process is available: @is
| No Format |
|---|
@is_dbreplicate_session is set to 1 |
...
MySQL
Only flag to identify that the sessoin session was spawned by apply APPLY process is available: context
| No Format |
|---|
context_info is set to 1 |
...