System Tablespace Size Increase While Running Impdp
(Doc ID 1590396.1)
Last updated on MARCH 29, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Goal
System tablespace has grown after the Data Pump import execution and the most larger table is argument$:
OWNER SEGMENT_NAME BYTES/1024/1024
--------------- ------------------------------ ---------------
...
SYS I_ARGUMENT2 7994
SYS I_ARGUMENT1 14189
SYS ARGUMENT$ 17307
A 10046 trace file showed as the top SQL statement:
insert into argument$( obj#,procedure$,procedure#,overload#,position#, sequence#,level#,argument,type#,default#,in_out,
length,precision#,scale,radix,charsetid,charsetform,properties,type_owner,type_name,type_subname,type_linkname,pls_type)
values (:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,:14,:15,:16,:17,:18,:19,:20,:21,:22,:23)
Why does the System tablespace increase continously during the Data Pump Import execution?
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 |