Table of Contents
This appendix describes how to solve problems that may occur while using Tibero
Problem
$ tbsql SYS/tibero tbSQL 6 TmaxData Corporation Copyright (c) 2008-. All rights reserved. TBR-2131: Generic I/O error
The above message may be displayed when accessing Tibero's database using the tbSQL utility.
Solution
Check if Tibero starts.
The solution is different depending on whether Tibero starts.
If Tibero does not start:
Check if the Tibero process is running using the tbctl command:
$ tbctl pid ... The Tibero process does not exist.
The ps and grep commands can also be used to check if the Tibero process is running:
$ ps -ef | grep tbsvr tibero 22919 22590 0 15:37 pts/10 00:00:00 grep tbsvr ... The Tibero process does not exist.
If the Tibero process does not exist, start Tibero using the tbboot command. For information about how to use the tbboot command, see “2.5.1. tbboot”.
If Tibero starts:
If the Tibero process is running as follows, but the environment settings for the server do not match those of a client, the database cannot be accessed.
$ ps -ef | grep tbsvr tibero 32036 1 0 20:00 pts/7 00:00:00 tbsvr -t ... tibero 32038 32036 0 20:00 pts/7 00:00:00 tbsvr_MGWP -t ... tibero 32039 32036 0 20:00 pts/7 00:00:00 tbsvr_FGWP000 -t ... tibero 32040 32036 0 20:00 pts/7 00:00:00 tbsvr_FGWP001 -t ... tibero 32041 32036 0 20:00 pts/7 00:00:00 tbsvr_PEWP000 -t ... tibero 32042 32036 0 20:00 pts/7 00:00:00 tbsvr_PEWP001 -t ... tibero 32043 32036 0 20:00 pts/7 00:00:00 tbsvr_PEWP002 -t ... tibero 32044 32036 0 20:00 pts/7 00:00:00 tbsvr_PEWP003 -t ... tibero 32045 32036 0 20:00 pts/7 00:00:00 tbsvr_AGNT -t ... tibero 32046 32036 0 20:00 pts/7 00:00:00 tbsvr_DBWR -t ... tibero 32047 32036 0 20:00 pts/7 00:00:00 tbsvr_RCWP -t ... tibero 32057 30048 0 20:00 pts/7 00:00:00 grep tbsvr
Check the client settings in the tbdsn.tbr file under the $TB_HOME/client/config directory.
<tbdsn.tbr>
tibero=( (INSTANCE=(HOST=localhost) (PORT=8629) (DB_NAME=tibero) ) )
In the above example, the host is set to localhost and its port number is set to 8629. Check if the settings are the same as those on the server.
Check the following:
<$TB_HOME/config/$TB_SID.tip>
# -----*----- conf -----*-----
#
# Tibero initialization parameter
#
LISTENER_PORT=6666
......
Check the settings for the server in the $TB_SID.tip file under the $TB_HOME/config directory.
In the above example, the port number is not the same as the client, so Tibero's database cannot be accessed.
In addition, if a port number is not specified, an arbitrary port number is specified in Tibero for testing. This may cause a conflict between port numbers. Therefore, specify the server and client with the same port number for the reliable operation of Tibero.
However, if the database is locally accessed, Tibero starts even though the port number in tbdsn.tbr is different from that in $TB_SID.tip. If the database is remotely accessed, Tibero only starts when the port numbers of the server and client are the same.