My Oracle Support Banner

Logon Triggers are not Fired During Expdp and Impdp Sessions (Doc ID 739508.1)

Last updated on MAY 12, 2021

Applies to:

Oracle Database Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.1.0.7 [Release 10.1 to 11.1]
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
This problem can occur on any platform.

NOTE: In the testcase content below, the user information and metadata used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Symptoms

You created:

- a non-global application context
- a user logon schema trigger which sets a value for that context
- a table
- a row trigger which attempts to read that context value out

Then you export/import the table using DataPump (expdp/impdp) and the values set by context in logon trigger are missing.

Steps to reproduce:

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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