My Oracle Support Banner

DataPump Metrics=Y Can Sometimes Incorrectly Show Negative Elapsed Time (Doc ID 2301604.1)

Last updated on JUNE 06, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2.0.1 [Release 12.1 to 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Goal

NOTE: The document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

The METRICS=Y parameter for DataPump export and import will generate additional log information showing the elapsed time required to export or import object types or individual tables in the DataPump job.
In some cases the elapsed time can be displayed as a negative number as shown below:

24-AUG-17 19:36:21.553: . . exported "TESTUSER"."TABLE1" 562.8 MB 339497 rows in 248 seconds
24-AUG-17 19:38:09.925: . . exported "TESTUSER"."TABLE2" 189.5 MB 174462 rows in 108 seconds
25-AUG-17 03:07:01.218: . . exported "TESTUSER"."TABLE3" 253.2 GB 543008 rows in -59468 seconds
25-AUG-17 06:38:21.841: . . exported "TESTUSER"."TABLE4" 253.3 GB 498805 rows in 12680 seconds
25-AUG-17 06:38:26.864: . . exported "TESTUSER"."TABLE5" 154.7 MB 1734347 rows in 5 seconds

Why would a table in the export logfile show a negative elapsed time value? 

Solution

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
Goal
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.