Docs Home

Troubleshooting

This chapter describes how to solve problems that can occur after Tibero is installed.

User Configuration Files

TB_HOME

Issue

TBR-2048 : Data source was not found.

If the property TB_HOME is not set or is set improperly, or if the user configuration file is not applied after Tibero is installed, this message may be displayed when trying to connect to the tbSQL utility.

Solution

Check the TB_HOME property in the user configuration file, change the value if necessary, and then apply the file to the system.

LD_LIBRARY_PATH

Issue

tbsql: error while loading shared libraries: libtbcli.so: 
cannot open shared object file: No such file or directory

If the property LD_LIBRARY_PATH is not set or is set improperly, or if the user configuration file is not applied after Tibero is installed, this message may be displayed when trying to connect to the tbSQL utility.

Solution

Check the LD_LIBRARY_PATH property in the user configuration file, change the value if necessary, and then apply the file to the system.

TB_SID

Issue

ERROR: environment variable $TB_SID is not set
tbdown: environment variable TB_HOME or TB_SID is not set.
Tip file open failure.: No such file or directory
tbdown failed. proc info file is deleted.

If TB_SID is not set, this message may be displayed when the tbboot or tbdown command is executed.

Solution

Check the TB_SID property in the user configuration file, change the value if necessary, and then apply the file to the system.

TAC Installation

The following describes how to resolve issues that can occur after Tibero is installed in a TAC environment.

Adding a Node

Accessing a tip File

Issue

tip file does not exist / reading tip file failed / malformed tip file

If a configuration file (.tip) cannot be found when a node is added, this message may be displayed.

Solution

Check whether the Tibero instance's $TB_SID.tip exists in the corresponding path by referring to TB_HOME and TB_SID.

Accessing TAC

Issue

extracting information from the existing cluster failed

To add a node, an existing node's setting values are necessary. If trying to access an existing node fails, this message may be displayed.

Solution

  • Check that TB_HOME and TB_SID are set properly.

  • Check that the existing node can be accessed through tbsql.

  • If an existing node does not work, start the node with the tbcm, tbboot commands then try to add the node again.

Transferring an scp File

Issue

Remote file transfer failed! / Remote configuration export failed!

If transferring Tibero installation files to a new node fails, this message may be displayed.

Solution

  • Check whether the current node can access the node to be added using ping or ssh.

  • If the current node cannot access the node to be added, check the settings for account synchronization, networking, and any firewalls.

TPR-Related Error When Using a TAC Raw Device

Issue

The SYSSUB tablespace, which contains TPR-related tables, was added starting from Tibero 5.0 r61295. During the system schema configuration portion of installing and patching, the syssub001.dtf file is automatically created in the directory $TB_ HOME/database/$TB_SID. However, if the property DB_CREATE_FILE_DEST is set to a specific location, the file is created at that location.

However, in an environment using a TAC raw device, the file is created on the local disk of the node processing the system schema. This results in an error that prevents other nodes from accessing the SYSSUB tablespace. The same error occurs in a shared disk environment when the property, DB_CREATE_FILE_DEST, is not set correctly.

Solution

Recreate the SYSSUB tablespace as follows:

  1. Delete the existing tablespace.

SQL> DROP TABLESPACE SYSSUB INCLUDING CONTENTS AND DATAFILES;

  1. Create a new tablespace.

SQL> CREATE TABLESPACE SYSSUB DATAFILE '<SYSSUB path>/syssub001.dtf' ...;

  1. Execute the following script.

$TB_HOME/scripts/tpr.sql
$TB_HOME/scripts/pkg/_pkg_dbms_tpr.tbw

Miscellaneous

Port Number

Issue

Listener port = 8629
bind() failed: Address already in use.
Error: Timedout while trying to open port 8629 
Check if there are any Tibero instances running. 
Tibero instance startup failed!

This error occurs when the specified port number is already in use when executing the tbboot command.

Solution Check whether the instance is already in use or modify the port number set in the $TB_SID.tip file in $TB_HOME/client/config.

dbtimezone

Recommendation

The dbtimezone is the reference timezone value used for storing the timestamp with local timezone data to database. Since this value is internally processed in the database, it is not recommended to modify it, because this requires unnecessary operations leading to performance degradation.

PreviousAppendixNextMounting a CD-ROM

Last updated