Impdp Doesn't Load Large Table Data - 0 Out Of 1268185777 Rows
(Doc ID 1987476.1)
Last updated on MAY 17, 2021
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterOracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Information in this document applies to any platform.
Symptoms
On 11.2.0.3 when importing 4 of the largest tables, the DataPump log reported 0 rows imported and no errors were raised.
This process of exporting and importing had worked fine in the past.
Master table "SYSTEM"."SYS_IMPORT_TABLE_06" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_TABLE_06": system/********@ PARFILE=parfile.txt
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "<OWNER>"."<TABLE 1>" 185.5 GB 0 out of 6,997,967,388 rows
. . imported "<OWNER>"."<TABLE 2>" 188.6 GB 0 out of 1,261,576,475 rows
. . imported "<OWNER>"."<TABLE 3>" 171.1 GB 0 out of 2,228,112,482 rows
. . imported "<OWNER>"."<TABLE 4>" 45.58 GB 0 out of 1,160,818,356 rows
Starting "SYSTEM"."SYS_IMPORT_TABLE_06": system/********@ PARFILE=parfile.txt
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "<OWNER>"."<TABLE 1>" 185.5 GB 0 out of 6,997,967,388 rows
. . imported "<OWNER>"."<TABLE 2>" 188.6 GB 0 out of 1,261,576,475 rows
. . imported "<OWNER>"."<TABLE 3>" 171.1 GB 0 out of 2,228,112,482 rows
. . imported "<OWNER>"."<TABLE 4>" 45.58 GB 0 out of 1,160,818,356 rows
Export shows, the data was actually exported:
. . exported "<OWNER>"."<TABLE 1>" 185.5 GB 6997967388 rows
. . exported "<OWNER>"."<TABLE 2>" 188.6 GB 1261576475 rows
. . exported "<OWNER>"."<TABLE 3>" 171.1 GB 2228112482 rows
. . exported "<OWNER>"."<TABLE 4>" 45.58 GB 1160818356 rows
. . exported "<OWNER>"."<TABLE 2>" 188.6 GB 1261576475 rows
. . exported "<OWNER>"."<TABLE 3>" 171.1 GB 2228112482 rows
. . exported "<OWNER>"."<TABLE 4>" 45.58 GB 1160818356 rows
Changes
The only change that occurred was that the size of the table increased.
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 |