Skip to main content

Search

Welcome to Tibero GTS!

TBR-8167 Error Occurs During PSM Compilation Using Tibero to Tibero DB Link

Document Type | Troubleshooting

Category | Patch/Upgrade

Applicable Product Versions | 7FS01, 7FS02, 7FS02PS

Document Number | TPATS011

 

Issue

Note
This issue occurred in Tibero7 fs02 version.
During the process of compiling PSM using Tibero to Tibero DB Link, the compilation fails with the error TBR-8167: The computed column length is too long.
 
Below is the information for SOURCE DB and TARGET DB.
[SOURCE DB]
- TIBERO VERSION : TIBERO 7
- character set : MSWIN949
- _ALLOW_DIFF_CHARSET_INSTANCE=Y in use
[TARGET DB]
- TIBERO VERSION : TIBERO 7
- character set : UTF8
- _ALLOW_DIFF_CHARSET_INSTANCE=Y in use
 

Cause

When querying a table on a remote DB with a different character set, size adjustment and verification are performed even on unused VARCHAR type columns, causing unnecessary errors.
If the source DB and target DB of the DB Link have different character sets, operations involving large columns in CTAS/PSM may not function correctly.
 
For this reason, size adjustment is performed for all VARCHAR columns of the remote table, and if the adjusted size exceeds the allowable limit, the TBR-8167 error occurs.
In this case, the problematic remote table had a large VARCHAR column that was actually unused, but size adjustment and verification were performed regardless of usage, resulting in the error.
 
 

Solutions

When querying tables between DBs with different character sets via CTAS/PSM, apply the patch (315355b) which improves the functionality to disable size checking of VARCHAR columns through parameter settings.
Caution
Apply the patch through technical support provided by Tmax Tibero.
 
After applying the patch, setting the parameter _ALLOW_DIFF_CHARSET_INSTANCE to FORCE allows ignoring throws caused by VARCHAR column size adjustment, enabling the operation to proceed normally without errors.
 
 
 

Related to