Skip to main content
๐Ÿ““ Tibero Online Manual Click here ๐Ÿ““

Search

Welcome to Tibero GTS!

LOB Column Tablespace Not Changed When Using tbexport remap_tablespace

Document Type | Troubleshooting

Category | Migration

Applicable Product Version | 6FS07

Document Number | TMITS006

 

Issue 

In Tibero 6 (DB 6.0 FS07_CS_2005) version, when performing tbexport with the remap_tablespace option specified, the tablespace for LOB columns does not change.
 

1. Perform tbexport on a table with LOB columns including the remap_tablespace option.

$ tbexport username=sys password=tibero sid=tibero port=8629 file=lob_col.dat log=lob_col.log table=tibero.test remap_tablespace=tibero:test script=y

 

2. Check the DDL script generated by tbexport.

You can confirm that while the tablespace for the table has been changed, the tablespace for the LOB has not been changed.

SQL> @ISU_CRYPT_BLOCK.sql
At line 179, column 48:
                       if((i + 1) % 16 == 0 && i != 0){                                                                                                                                                                                     
                                              ^
Enter value for 'i':

 

 

Cause

When performing table mode export, the tablespace name is not taken as the remapped tablespace name but rather as the original tablespace name, causing the DDL statement to be generated incorrectly and resulting in this issue.
 
 
 

Solutions

1. Replace with binary including FS07_282928a_expimp patch

From Tibero6 FS07PS version onward, this is fixed. Apply the FS07_282928a_expimp patch to resolve the issue.

 

2. Check LOB table DDL and manually specify tablespace before performing tbimport

By using the script=y option during tbexport, check the DDL for the LOB table and manually modify the tablespace. Then create the table and perform tbimport with the ignore=y option to transfer the data.

  • Generate script during tbexport
$ tbexport username=sys password=tibero sid=tibero port=8629 file=lob_col.dat log=lob_col.log table=tibero.test remap_tablespace=tibero:test
script=y
SCRIPT
Specifies whether to display the DDL script that creates schema objects during export.
  • Y : Displays the DDL script that creates schema objects.
  • N : Does not display the DDL script that creates schema objects. (Default)
 
  • tbimport command
$ tbimport username=sys password=tibero sid=tibero port=8629 file=lob_col.dat table=tibero.test log=imp_lob_col.log script=y
ignore=y
IGNORE
Sets whether to ignore creation errors caused by existing schema objects during import.
  • Y : Ignores creation errors caused by existing schema objects.
  • N : Does not ignore creation errors caused by existing schema objects. (Default)
 
 

3. Re-perform tbexport/tbimport after changing Tibero Client

  • Client Change Procedure
3.1) Upload the client.tar file containing the patch to /home/{tibero OS username}
3.2) Extract client.tar
$ tar xvf client.tar
 
3.3) Change jar file paths in tbimport file
$ vi /home/{tibero OS username}/client/bin/tbimport
---------------------------
#Classpath
toolcom=/home/{tibero OS username}/client/lib/jar/toolcom.jar
expimp=/home/{tibero OS username}/client/lib/jar/expimp.jar
jdbc=/home/{tibero OS username}/client/lib/jar/internal-jdbc-14.jar
logger=/home/{tibero OS username}/client/lib/jar/msllogger-14.jar
---------------------------
 
3.4) Perform tbexport and tbimport
Execute in the directory where the changed Client (tbimport utility) exists.
$ tbexport username=sys password=tibero sid=tibero port=8629 file=lob_col.dat log=lob_col.log table=tibero.test remap_tablespace=tibero:test 
script=y
$ tbimport username=sys password=tibero sid=tibero port=8629 file=lob_col.dat table=tibero.test log=imp_lob_col.log script=y ignore=y

 
 
 
 
 

 

Related to