Skip to main content

Search

Welcome to Tibero GTS!

ORA-00403 Occurs During Migration via Oracle → Tibero TableMigrator

Document Type | Troubleshooting

Category | Migration

Applicable Product Version | 6FS07

Document Number | TMITS007

 

Issue

Note
Affected Version: Tibero6 FS07 / Oracle 11g + SunOS / TableMigrator 262224

When migrating tables containing XML type from Source (Oracle) using TableMigrator, the PGA memory on the Source (Oracle) side is consumed.

 

Scenario

1. Created on Source

SQL > create table t322393(
ROWCNT number
, C1 number
, C2 varchar2(100)
, C3 char(10)
, C4 date not null
, C5 timestamp
, C6 interval day to second
, C7 interval year to month
, C8 raw(16)
, C9 nchar(15)
, C10 nvarchar2(10)
, C11 varchar(10)
, C12 blob
, c13 xmltype
)
TABLESPACE ts322393 
PCTFREE 10
PCTUSED 0
INITRANS 1
MAXTRANS 255
LOGGING
NOCOMPRESS 
DISABLE ROW MOVEMENT 
NOPARALLEL;
 

2. Sample Data Insert

SQL > insert into t322393
( rowcnt 
, C1 
, C2 
, C3 
, C4 
, C5 
, C6 
, C7 
, C8 
, C9 
, C10
, C11
, C12
, c13
)
(
select 
level
,level+1
,to_date(to_char(trunc(dbms_random.value(2000,2010)))||'0101','yyyymmdd')+trunc(dbms_random.value(1,365))
,to_date(to_char(trunc(dbms_random.value(2000,2100)))||'0101','yyyymmdd')+trunc(dbms_random.value(1,365))
,sysdate
,sysdate
,INTERVAL '30' MINUTE
, INTERVAL '01-02' YEAR TO MONTH
,SYS_GUID()
,'test'
,'test'
,'2000'
,lpad('A',4000,'A')
, '
Name 
Name2 
Name 
Name2 
' 
from dual connect by level <= 200000);
SQL > commit;
 

3. Migrate the table via TableMigrator on Target

 

4. Check memory on Source (Oracle) with the following query

SQL > select s.sid,s.pid, s.PROG_NAME, round(s.PGA_USED_MEM/1024/1024/1024, 2) ||' GB' PGA from v$session s where s.PROG_NAME= 'Table Migrator[1]';
 
 
 
 

Cause

The detailed process of the memory leak is as follows.
  1. When using Table Migrator, the XMLTYPE column data is retrieved using the getClobVal() function.
  2. During this process, an internal Oracle Temp LOB is created.
  3. However, the cleanup of this Temp LOB is not properly performed, causing PGA usage to increase until the session ends.
Therefore, to prevent this issue, it is necessary to use an improved version of the T-up binary.
 
 
 
 
 

Solutions

This issue is resolved by using the T-up binary with the applied improvement patch. (Improvement patch: FS01_2404a_tup)
Caution
Apply the patch through technical support provided by Tmax Tibero. 

 

 
 
 
 
 
 
 

Related to