Caution

Apply the patch through technical support provided by Tmax Tibero.

-- Test scenario after patch application

# Create Tibero to Tibero dblink
create database link tlink01 connect to tibero identified by 'tmax' using 'tibero';
create database link tlink02 connect to tibero identified by 'tmax' using 'tibero';

# Create Tibero to Oracle dblink
create database link olink01 connect to lkh identified by 'tibero' using 'gw_orcl19';
create database link olink02 connect to lkh identified by 'tibero' using 'gw_orcl19';

[Execute on both Oracle and Tibero]
create table t1_long (c1 varchar2(10), c2 long);
create table t2_long (c1 varchar2(10), c2 long);
insert into t2_long values('a', 'a');
insert into t1_long values('a', 'a');

create table t1_clob (c1 varchar2(10), c2 clob);
create table t2_clob (c1 varchar2(10), c2 clob);
insert into t2_clob values('a', 'a');
insert into t1_clob values('a', 'a');
commit;


# Insert test
1. Tibero to Tibero (Remote to Remote)
insert into t1_long@tlink01 select * from t2_long@tlink02;

2. Oracle to Oracle (Remote to Remote)
insert into t1_long@olink01 select * from t2_long@tlink01;

3. Cross-database remote to remote
insert into t1_long@tlink01 select * from t2_long@olink01;
insert into t1_long@olink01 select * from t2_long@tlink01;

# Update test 
1. Tibero to Tibero (Remote to Remote)
update t1_long@tlink01 t1 set (c1, c2) = (select c1, c2 from t2_long@tlink02);

2. Oracle to Oracle (Remote to Remote) 
update t1_long@olink01 t1 set (c1, c2) = (select c1, c2 from t2_long);

3. Cross-Database Remote to Remote
update t1_long@tlink01 t1 set (c1, c2) = (select c1, c2 from t2_long@olink01);
update t1_long@olink01 t1 set (c1, c2) = (select c1, c2 from t2_long@tlink01);

-- All should execute normally without signals and output "1 row inserted."

Note

If the patch is not applied, the issue can be mitigated by using Lob instead of Long type.