Skip to Content
Author's profile photo Former Member

cscheck connectivity test on Unix / Linux

cscheck is a handy tool which uses the connection server libraries to connect to a database.  It is a good way to validate that the connection server libraries (which are used by Desktop Intelligence / Web Intellligence and Connection Server) are able to connect to your database.

 

To use the tool:

 First, source env.sh which can be found in the bobje/setup directory:

 

. ~/FINAL/bobje/setup/env.sh

or

source ~/FINAL/bobje/setup/env.sh

 

Next, navigate to the bobje/enterprise120/linux_x86/dataAccess/RDBMS/connectionServer/tools directory (the linux_x86 in my example may be something else depending on which flavor of Unix / Linux you are on)

Next, run cscheck with the list parameter to get a list of drivers:

 [bobj@RH31 tools]$ ./cscheck list

——————————————————————————-
 Oracle Client
   Oracle 9
   Oracle 10
   Oracle 11
 Sybase Open Client
   Sybase Adaptive Server 12
   Sybase Adaptive Server 15
 Informix ODBC Driver
   Informix XPS 8.4
   Informix XPS 8.5
   Informix Dynamic Server 7.3
   Informix Dynamic Server 2000
   Informix Dynamic Server 10
   Informix Dynamic Server 11
 Teradata ODBC Driver
   Teradata V2 R5
   Teradata V2 R6
   Teradata 12
 ODBC Drivers
   Generic ODBC Datasource
   Generic ODBC3 Datasource
   HP Neoview
   Sybase ASIQ 12
   Sybase SQL Anywhere 10
   Red Brick Decision Server 6.x
   MS SQL Server 7.x
   MS SQL Server 2000
   MS SQL Server 2005
….

To test connectivity, first determine which driver you are using.  To check, open designer on a Windows machine and check your connection there.

In this example, I’m using an ODBC Driver and a MS SQL Server 2005 connection.

[bobj@RH31 tools]$ ./cscheck ping -m local -c “ODBC Drivers” -d “MS SQL Server 2005” -u myDatabaseUser -p myDatabasePassword -s SQL

——————————————————————————-
BusinessObjects Configuration:
Version: Not Defined
Build: Not Defined
Network Layer: ODBC
DBMS Engine: MS SQL Server 2005
Language: en
Charset: ISO-8859-1
Library: /home/bobj/xi3.1/bobje/enterprise120/linux_x86/dataAccess/RDBMS/connectionServer/libdbd_wmssql.so
SBO: /home/bobj/xi3.1/bobje/enterprise120/linux_x86/dataAccess/RDBMS/connectionServer//odbc/odbc.sbo
RSS: /home/bobj/xi3.1/bobje/enterprise120/linux_x86/dataAccess/RDBMS/connectionServer//odbc/sqlsrv.rss
PRM: /home/bobj/xi3.1/bobje/enterprise120/linux_x86/dataAccess/RDBMS/connectionServer//odbc/sqlsrv.prm
Strategies: /home/bobj/xi3.1/bobje/enterprise120/linux_x86/dataAccess/RDBMS/connectionServer//odbc/sqlsrv.stg
Middleware and DBMS Configuration:
Charset: UTF8
Driver version: 05.30.0078 (b0054, U0047)
Driver API level: 03.52
ODBC Manager version: 3.52.0000
ODBC Manager API level: 03.52.0000
DBMS name: Microsoft SQL Server
DBMS version: 09.00.4035
——————————————————————————-

In this example, I used ODBC Drivers.  Had I been using Oracle, I’d instead enter “Oracle Client”

Had I been using Oracle 10 I’d enter “Oracle 10” for the -d switch

Finally, the -s for server is my ODBC DSN name.  With Oracle, I’d use the tnsname.  Same for any other database – use whatever database alias you have defined.

 

As you can see, the tool gives a lot of information such as client version, configuration files and even the version of your database server.  In addition, it gives error messages which can help you narrow down or even resolve problems.

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.