Thanks for the question, Arun.
Asked: July 14, 2017 - 1:11 pm UTC
Last updated: July 21, 2017 - 1:06 am UTC
Version: 11.2.0.4
Viewed 1000+ times
You Asked
I queried the DBA_FEATURE_USAGE_STATISTICS to check if advance compression is being used anywhere. One specific record caught my attention. Here is the row in a single record format:
DBID: Suppressed
NAME: Oracle Utility Datapump (Export)
VERSION: 11.2.0.4
DETECTED_USAGES: 14
TOTAL_SAMPLES: 14
CURRENTLY_USED: TRUE
FIRST_USAGE_DATE: 04-APR-17 02:10:40 PM
LAST_USAGE_DATE: 06-JUL-17 01:21:38 AM
AUX_COUNT: 1262
FEATURE_INFO: Oracle Utility Datapump (Export) invoked: 1262 times, compression used: 18 times, encryption used: 0 times
LAST_SAMPLE_DATE: 06-JUL-17 01:21:38 AM
LAST_SAMPLE_PERIOD: 605197
SAMPLE_INTERVAL: 604800
DESCRIPTION: Oracle Utility Datapump (Export) has been used.
How do I interpret this information? Does this imply that between 4/4/17 and 7/6/17, data pump export was used 1262 times and advance compression was used 18 times? This does not make sense because I never run export against this database this frequently. Worst case scenario, one export a day. I have also verified the scripts and they do not use advance compression (no data compression). So, what is this information telling me?
Thanks,
Arun
and Connor said...
Your interpretation is correct, so the task now is to work out why.
(Once you're on 12c, you can directly use the audit facilities to track data pump operations)
Things to take into consideration
- anyone with the right privs can call datapump (even via PLSQL)
- is anything from OEM doing data pump jobs without your knowledge
- do you have the SYSMAN schema (some bugs with feature tracking on compressed tables in this schema)
- do you have an HCC tables
If all else fails, time to talk to Support to eliminate a bug being the cause, and then start hunting down who is running datapump jobs
Is this answer out of date? If it is, please let us know via a Comment