Skip to main content

Search

Welcome to Tibero GTS!

system.vbs Execution Failure During New Tibero Installation on Windows Environment (Referencing Existing DSN)

Document Type | Troubleshooting

Category | Patch/Upgrade

Applicable Product Version | 6FS07

Document Number | TINTI013

 

Issue

During the process of newly installing Tibero on a Windows server, an issue occurs where the system.vbs script fails to execute properly at the stage of referencing previously configured DSN information.
 
 
 

Cause

When executing system.vbs, it attempts to connect to the database based on the %TB_SID% value set in the Windows environment variables. However, if a DSN with the same name as %TB_SID% already exists in the existing ODBC settings, it attempts to connect to the database defined by that DSN, resulting in the inability to run system.vbs.
 

Add CLI Parameters to tbdsn.tbr and Check Client Logs

#TBCLI_LOG_LVL=TRACE
#TBCLI_LOG_DIR=C:\tibero_dump\cli

 

When DSN is Read

[DBG] cli_api_db:1871 odbc_get_dsn_info_for_win:dsn[0000000002D73324] svrname[tibero] username[000000000014DF20] passowrd[000000000014DEE0] real_svrname[000000000014DFF0]
[TRC] cli_api_db:1942 odbc_get_dsn_info BY IP/PORT:svrname[tibero] username[sys] password[tibero] ip[localhost] port[8610] dbname[tibero]
[TRC] cli_dbc.c :910 Use DSN info from odbc.ini
 
 

When No DSN Information is Registered

[DBG] cli_api_db:1871 odbc_get_dsn_info_for_win:dsn[0000000002CD2314] svrname[] username[000000000014EF80] passowrd[000000000014EF40] real_svrname[000000000014F050]
[TRC] cli_dbc.c :904 DSN info is not enough in odbc.ini
 
 
 

Solutions 

  1. Delete the DSN registered in the existing ODBC.
  2. When installing Tibero anew, change the %TB_SID% value and register the environment variable so that it does not reference the existing DSN.
 
 
 
 
 
 

Related to