Connection Server Troubleshooting Guide - … sysmaster ; select is_ansi, name from sysdatabases ;...

Connection Server TroubleshootingGuide

BusinessObjects Connection Server XI 3.1

© 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects ownsthe following United States patents, which may cover products that are offered and

Copyright

licensed by SAP BusinessObjects and/or affiliated companies: 5,295,243;5,339,390; 5,555,403; 5,590,250; 5,619,632; 5,632,009; 5,857,205; 5,880,742;5,883,635; 6,085,202; 6,108,698; 6,247,008; 6,289,352; 6,300,957; 6,377,259;6,490,593; 6,578,027; 6,581,068; 6,628,312; 6,654,761; 6,768,986; 6,772,409;6,831,668; 6,882,998; 6,892,189; 6,901,555; 7,089,238; 7,107,266; 7,139,766;7,178,099; 7,181,435; 7,181,440; 7,194,465; 7,222,130; 7,299,419; 7,320,122 and7,356,779. SAP BusinessObjects and its logos, BusinessObjects, Crystal Reports®,Rapid Mart™, Data Insight™, Desktop Intelligence™, Rapid Marts®, WatchlistSecurity™, Web Intelligence®, and Xcelsius® are trademarks or registeredtrademarks of Business Objects, an SAP company and/or affiliated companies inthe United States and/or other countries. SAP® is a registered trademark of SAPAG in Germany and/or other countries. All other names mentioned herein may betrademarks of their respective owners.

2009-01-27

ContentsIntroducing Connection Server troubleshooting guide 5Chapter 1

About the Connection Server troubleshooting guide...................................6Audience of the guide.............................................................................6User requirements..................................................................................6

Configuring middleware 9Chapter 2

Configuring middleware.............................................................................10DB2 iSeries middleware.......................................................................11DB2 UDB middleware..........................................................................11Informix middleware.............................................................................12Ingres middleware................................................................................13MySQL middleware..............................................................................17Netezza middleware.............................................................................18OLAP middleware................................................................................19OLE DB middleware.............................................................................20Oracle middleware...............................................................................20SQL Server middleware.......................................................................21Redbrick middleware............................................................................26Sybase ASE middleware......................................................................26Sybase IQ middleware.........................................................................27Teradata middleware............................................................................28

Tracing Connection Server 31Chapter 3

Activating Connection Server traces.........................................................32To activate traces of Connection Server in library mode......................33To activate traces of Connection Server in server mode......................33

Connection Server Troubleshooting Guide 3

To activate traces of Java connectivities..............................................35To trace Java connectivities with another framework...........................35To activate jobs and driver traces.........................................................36To activate traces of OLAP connectivities............................................36

Reading Connection Server traces............................................................37Activating ODBC traces.............................................................................38

Investigating errors 41Chapter 4

To avoid connection failures at startup......................................................42To debug Connection Server at startup.....................................................43General diagnosis......................................................................................44

To check your system before further investigations.............................44Miscellaneous checks..........................................................................45To do a first diagnostics on Microsoft Windows...................................48To do a first diagnostics on UNIX.........................................................48Investigating further..............................................................................49

Selecting a driver manager on UNIX.........................................................49

Index 51

4 Connection Server Troubleshooting Guide

Contents

Introducing ConnectionServer troubleshootingguide

1

About the Connection Servertroubleshooting guide

The Connection Server troubleshooting guide gives advice for dealing witherrors or connection failures you may encounter while using ConnectionServer. It helps you configure your environment to avoid errors and presentssolutions to Connection Server issues.

The guide involves the following:

• Configuring middleware• Tracing Connection Server• Investigating errors

Note:Unless specified, the guide relates to the Titan release and later. For moreinformation about Connection Server, refer to:• Data Access guide• Connection Server testing guide

Related Topics• Configuring middleware on page 10• Activating Connection Server traces on page 32• General diagnosis on page 44

Audience of the guide

The Connection Server troubleshooting guide is intended for Business ObjectsCustomer Support and Escalations teams and other clients of ConnectionServer who need to diagnose problems.

User requirements

The Connection Server troubleshooting guide assumes that users have thefollowing knowledge and experience:

• Java programming language• C++ programming language


Introducing Connection Server troubleshooting guide1 About the Connection Server troubleshooting guide

• drivers• database middleware• databases and SQL query language• Apache Ant• Business Objects application architecture• Connection Server API


1Introducing Connection Server troubleshooting guideAbout the Connection Server troubleshooting guide


Introducing Connection Server troubleshooting guide1 About the Connection Server troubleshooting guide

Configuring middleware

2

Configuring middlewareThe following sections present useful information for configuring middlewareof specific databases and testing the connection established. You are advisedto follow these instructions in order to avoid any middleware configurationissue that may cause Connection Server process failures. If you experienceerrors that may be caused by middleware issues, check in the followingsections you configure middleware correctly.

Note:The following sections of middleware configuration use LD_LIBRARY_PATHas environment variable for library files on UNIX. However the variable nameactually differs depending on the UNIX flavor you are configuring:• LD_LIBRARY_PATH is for Linux or Solaris• SHLIB_PATH is for HP-UX• LIBPATH is for AIX

Related Topics• DB2 iSeries middleware on page 11• DB2 UDB middleware on page 11• Informix middleware on page 12• Ingres middleware on page 13• MySQL middleware on page 17• Netezza middleware on page 18• OLAP middleware on page 19• OLE DB middleware on page 20• Oracle middleware on page 20• SQL Server middleware on page 21• Redbrick middleware on page 26• Sybase ASE middleware on page 26• Sybase IQ middleware on page 27• Teradata middleware on page 28


Configuring middleware2 Configuring middleware

DB2 iSeries middleware

The following section describes how to configure the DB2 Client Accessmiddleware for ODBC to connect to DB2 iSeries databases. You can onlyinstall this middleware on Microsoft Windows, while DB2 iSeries is availableon AS/400.

Make sure you install the appropriate ODBC driver and that is synchronizedwith the DB2 database you want to use.

DB2 UDB middleware

The following section describes how to configure the DB2 UDB middlewarefor all DB2 databases.

1. Install the middleware.2. To create a connection, enter the following commands in the command

line tool:

db2catalog tcpip node DB5R1_KO remote kolda server 446catalog database kolda as DB5R2_KO at node DB5R1_KO authentication dcs

3. Source the DB2 profile.4. Configure the environment by editing .bash_profile, for example:

. /export/home/db2inst9/sqllib

5. To test the connection, enter the following commands:

connect to DB5R2_KO user rdaqc1 using rdaqc1

Note:Alternatively, use the Configuration Assistant provided by IBM DB2.

Note:To configure the middleware in a different character set, set DB2CODEPAGEenvironment variable to:• 1208 for Unicode management.• 950 and DB2COUNTRY to 88 for Chinese management.


2Configuring middlewareConfiguring middleware

Informix middleware

You can connect to different Informix servers, such as Informix Dynamic andInformix XPS, by using a single client called Informix Client SDK. To configurean ODBC connection through an Informix middleware, use Informix Setnet32tool.

On Microsoft Windows:

1. In the Environment tab, set the INFORMIXDIR and INFORMIXSQLHOSTSvariables.

2. In the Server Information tab, specify values of the server you want toaccess.

3. Edit the hosts file with the IP address of the server.

On UNIX:1. Configure the environment by editing .bash_profile, for example:

#INFORMIXexport INFORMIXDIR=/usr/local/BD/isdk290export INFORMIXSQLHOSTS=$INFORMIXDIR/etc/sqlhostsexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$INFORMIXDIR/lib:$INFORMIXDIR/lib/cli:$INFORMIXDIR/lib/esqlexport PATH=$INFORMIXDIR/bin:$PATH

2. Configure the datasource by editing the odbc.ini file, as follows:

[ODBC Data Sources]ids10=INFORMIX 3.33 32-BIT

[ids10]Driver=/usr/local/BD/isdk290/lib/cli/iclit09b.soServer=ids10Database=dsdb01[ODBC]UNICODE=UTF-8

3. Edit the sqlhosts and /etc/hosts files, for example:

#demo_on onipcshm on_hostname on_servername#demo_se seipcpip se_hostname sqlexecids10 ontlitcp 10.6.61.201 7000



The Informix database can be either ANSI or NON-ANSI. To know whichkind of database you are using, execute the following commands:

database sysmaster ;select is_ansi, name from sysdatabases ;

If the resulting is-ansi is 1, this means the database is ANSI.

Note:To avoid an unexpected behavior with DECIMAL number format onNON-ANSI databases, select the Describe Decimal Floating Point asSQL_REAL/SQL_DOUBLE option in the IBM Informix ODBC Driver Setup dialogbox on Microsoft Windows. On UNIX, edit the odbc.ini file with the DESCRIBEDECIMALFLOATPOINT parameter set to 1.

To test the connectivity, you can use the isql tool with the following syntax:

isql host-name user-name password

Ingres middleware

The following section describes how to configure the Ingres databasemiddleware on Microsoft Windows and on Linux. To configure the middleware,you must do the following:

• Set the Ingres virtual node.• Configure the Ingres datasource.


1. Install the Ingres database client.

Note:Select "Typical Client" on step 2.

2. Open the Ingres network utility from the Start menu.3. To set the Ingres node, fill in the fields with your network details, for

example:



4. Do a test to verify that correct details are entered.5. Open the ODBC Data Source Administrator and create a connection to

the Ingres database.6. In the Ingres ODBC Administrator that opens, fill in the fields with the

required details, as follows:



7. Test the connection.

On Linux:

1. Extract setup files from the TAR file.2. As root user, run the install.sh file.

Note:Select Ingres client only.

3. Set the following environment variables:

export II_SYSTEM=/opt/Ingres/IngresII/export PATH=/opt/Ingres/IngresII/ingres/utility/:/opt/Ingres/IngresII/ingres/bin:$PATHexport LD_LIBRARY_PATH=/opt/Ingres/IngresII/ingres/lib:$LD_LIBRARY_PATH



4. To run the Ingres server, go to /opt/Ingres/IngresII/ingres/utilityand execute the ingstart command.

5. Create the node with netutil tool:a. Edit the netutilFeed.txt text file with the following:

create private login test evalkit evalkitcreate global connection test 172.25.70.69 tcp_ip IIcreate global attribute testauthentication_mechanism Kerberos

b. Go to /opt/Ingres/IngresII/ingres/bin and execute the followingcommand:

netutil -file netutilFeed.txt

6. Configure the datasource by editing the odbc.ini file as follows:

[ODBC]Trace =YesTraceFile = /home/cs01/logs/odbc.logTraceDll = /usr/odbc/lib/odbctrac.so

[ODBC Data Sources]evalkit_Ingres2006=Ingres

[evalkit_Ingres2006]#Driver=IngresDriver=/opt/Ingres/IngresII/ingres/lib/libiiodbcdriver.1.soDescription=IngresVendor=Ingres CorporationDriverType=IngresServer=testDatabase=bodb01ServerType=IngresPromptUIDPWD=WithOption=RoleName=RolePWD=DisableCatUnderscore=NAllowProcedureUpdate=NUseSysTables=NBlankDate=NDate1582=NCatConnect=NNumeric_overflow=YSupportIIDECIMAL=NCatSchemaNULL=NReadOnly=NSelectLoops=Y



Username=evalkitPassword=evalkit

Note:The server name should be the same as the one set for the Ingres node.

7. Test the connection with the isql tool:

isql evalkit_Ingres2006 evalkit evalkit -v

Note:Use -v to display error messages if any.

MySQL middleware

To configure a connnection through the MySQL middleware on MicrosoftWindows, install the ODBC client driver and create your ODBC datasource.

On UNIX, create the datasource as follows:

1. Configure the environment by editing .bash_profile, for example:

#unixODBCexport LD_LIBRARY_PATH =/home/sl01/unixODBC/lib:$LD_LIBRARY_PATH#MYSQLexport PATH=/home/sl01/MYSQL/mysql-connector-odbc-3.51.25-sol9/bin:$PATHexport LD_LIBRARY_PATH=/home/sl01/MYSQL/mysql-connector-odbc-3.51.25-sol9/lib:$LD_LIBRARY_PATH#ODBCINIexport ODBCINI=/home/deski/odbc.ini

2. Configure the datasource by editing the odbc.ini file:

[ODBC Data Sources]myodbc_sun= MySQL ODBC Driver

[myodbc_sun]Driver =/home/sl01/MYSQL/mysql-connector-odbc-3.51.25-sol9/libmyodbc3.soDescription = MySQL ODBC 3.51 Driver DSNSERVER = sf280re303PORT =USER = csdev7Password = passwordDatabase = BOE115



OPTION = 3SOCKET =

MySQL 5 middleware

To connect to the MySQL 5 database, you need to use the MySQL ODBCdriver 5.1.4. It is targeted to support Unicode for all operating systems.

If you want to use the previous version 3.51, which does not support Unicode,edit the odbc.sbo configuration file of Connection Server as follows:1. Locate the MySQL 5 section.2. Remove the following line:

<Library Platform="Unix64">dbd_wux32odbc3</Library>

3. Save the file.

Connection Server then loads the dbd_ux32odbc3 driver instead of thedbd_wux32odbc3 one.

Testing tool

To test the MySQL connectivity, you can use the isql tool, which is able totest any ODBC connectivity. Before testing on UNIX, you must install theunixODBC driver and set the path and library path of both unixODBC andMySQL driver in .bash_profile.

Use the following command syntax to run the isql tool either on MicrosoftWindows or UNIX:

Isql DSNname UserName Password

Netezza middleware

To configure a connnection through the Netezza middleware on MicrosoftWindows, install the ODBC client driver and create your ODBC datasource.





export ODBCINI=/export/user-name/ODBCTest/odbc.iniexport LD_LIBRARY_PATH=/usr/local/lib:/user-name/ODBCTest/DBs_Mira_Certification/nz/lib:$LD_LIBRARY_PATHexport PATH=$PATH:/user-name/ODBCTest/DBs_Mira_Certification/nz/bin:/usr/local/bin

2. Configure the datasource by editing the odbc.ini file, for example:

[ODBC Data Sources]NZSQL=Netezza DSN

[NZSQL]Driver = /usr/u/user-name/ODBCTest/nz/lib/libnzsqlodbc3.soDescription=Netezza DSNDatabase=boServer=127.0.1.10Port=5480Username=evalkitPassword=evalkit

To test the connectivity, you use the nzsql tool that comes with the Netezzamiddleware and located in the bin installation directory. Following is anexample of command you execute to run the nzsql tool:

nzsql -host 127.0.1.10 -port 5480 -u evalkit -pw evalkit -D bo

OLAP middleware

You find OLAP middleware to install in the \\tinos\OLAP network directory.

Note:

To install SAP BW middleware, do the following:

• Follow the instructions described in the TXT files of the\\tinos\OLAP\SAPBW\client\<SAP BW version> directory.

• Install the Integration Kit for SAP software that comes with theBusinessObject Enterprise build in the SAP folder of the \\Build-drops-lv\dropzone\...\ directory.



OLE DB middleware

OLE DB is a Microsoft Windows technology. Connection Server providesthe following drivers for OLE DB connectivity:

• dbd_woledb.dll for generic OLE DB• dbd_wsqloledb.dll for an SQL Server driver

Note:On Microsoft Windows, do not forget to install MDAC. You must not uninstallit.

To test the connection, you can use the RowsetViewer tool.

Oracle middleware

The following section describes how to configure the Oracle middleware andhow to check it by testing connections.


1. Uninstall any prior version of the middleware before installing it. Removethe Oracle installation folder, and remove the registries in HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE.

2. Install the Oracle client version you want to use.

Note:Make sure you use the lib32 folder when starting your Oracle client.

3. To add a datasource, do one of the following:• Select Oracle > Configuration and Migration Tools > Net

Configuration Assistant.• Configure the TNS by editing the tnsnames.ora file located in the

Oracle-home\client\NETWORK\ADMIN directory.

Note:If you add the NAMES.DEFAULT_DOMAIN parameter set to product.businessobjects.com in the sqlnet.ora file, you then do not need to specifythe domain each time you create a datasource alias. This file is locatedin the oracle-home\client\NETWORK\ADMIN directory.



4. To test the connection, use SQL*Plus or TOAD.

Note:To configure the middleware in a different language, modify the NLS_LANGregistry value, which is located in HKEY_LOCALE_MACHINE\SOFTWARE\ORACLE\Oracle-home.

On UNIX:

1. Install the Oracle client version you want to use.2. Configure the environment by editing .bash_profile, for example:

export ORACLE_HOME=/dbclients/solaris/10g2export TNS_ADMIN=/export/home/qaunix/TNSexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ORACLE_HOME/lib:$ORACLE_HOME/lib32export NLS_LANG=AMERICAN_AMERICA.UTF8export LC_ALL=en_US.UTF-8

3. Configure the TNS by editing the tnsnames.ora file located in the /export/home/qaunix/TNS directory, for example:

o10g2 =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = 172.25.70.185)(PORT =

1521)))(CONNECT_DATA =(SERVICE_NAME = o10g2)))

4. Use SQL*Plus to test the connectivity, with the following syntax:

sqlplus username/password@o10g2

SQL Server middleware

The following section describes how to configure the Microsoft SQL Servermiddleware. This only accepts an ODBC connectivity.

Note:For SQL Server 2005 and SQL Server 2008, you need to install the Nativeclient from the installation CD-ROM.



On Microsoft Windows, do not forget to install Microsoft Data AccessComponents (MDAC).

Note:You must not uninstall it.

On UNIX, you can only access the SQL Server middleware through aDataDirect ODBC driver. Do the following to create a datasource:


export MERANT_HOME=/usr/local/BD/DataDirect5.1/export LD_LIBRARY_PATH=$MERANT_HOME/lib:$LD_LIBRARY_PATH

2. Configure the datasource by editing the odbc.ini file, for example:

[ODBC Data Sources]sql2005_wx3=SQL Server

[sql2005_wx3]Driver=/usr/local/BD/DataDirect5.1/lib/ivmsss21.soDescription=SQL ServerAddress=10.6.61.197,1433Database=bodb01

Note:The library variable must not exceed 256 characters.

To test the connectivity, use WinSQL, ODBCTest, or Example tools. TheExample tool is located in the /usr/local/BD/DataDirect5.1/example/directory on UNIX.

Note:You can only use Example if you have installed a DataDirect ODBCnon-branded driver.

Specific UNIX settings

Note:The following section is only related to:• BusinessObjects Enterprise XI Release 2 Service Pack 5 (Jupiter SP5)

OR

• BusinessObjects Enterprise XI 3.1 Service Pack 2 (Titan SP2, that is,Connection Server Component 2.1 version)



AND

• MS SQL Server 2000 SP4 and MS SQL Server 2005 SP2

Data Access supports the use of DataDirect ODBC 5.3 drivers for MS SQLServer databases on all UNIX platforms. These drivers can be either non-branded or branded (OEM) drivers.

The Connection Server default settings allow the non-branded ODBC driverto work seamlessly with your current configuration settings. If you havealready deployed a driver in your environment, you will be able to install thenon-branded driver without any configuration change.

The branded DataDirect drivers are provided as part of the BOE installationand can only be used with BOE products such as Web Intelligence, DesktopIntelligence, and Crystal Reports. If you want to install the DataDirect brandeddriver, follow the instructions below.

Installing the DataDirect branded driver1. Install the BOE release on UNIX, for example Sun Solaris.2. Locate the DataDirect branded driver files in boe-install-dir/enter

prise115/solaris_sparc/odbc directory, where boe-install-dirstands for the BOE installation directory.

Note:This location is valid for both releases.

Configuring the data access for the DataDirect branded driver

You configure the use of DataDirect ODBC branded (OEM) or non-brandeddrivers in the odbc.sbo file, which is located in the connectionserver-install-dir/connectionServer/odbc directory.

The Use DataDirect OEM Driver parameter of the DataBase sections isset to No by default. This means the data access is configured by default towork for non-branded drivers.

1. To enable the use of DataDirect 5.3 branded drivers, set the parameterof the appropriate DataBase section to Yes.

2. Do one of the following:



• If you have installed Titan SP2, add the following path to LD_LIBRARY_PATH environment variable:

boe-install-dir/bobje/enterprise120/platform-name/odbc/lib

where platform-name is the UNIX flavor used.• If you have installed Jupiter SP5, skip this step and go to step 3.

3. Edit the following lines in the env.sh file located in the boe-install-dir/setup directory:

DEFAULT_ODBCFILE=boe-install-dir/defaultodbc.iniExport DEFAULT_ODBCFILEODBC_HOME="$BINDIR/odbc"Export ODBC_HOMEODBCINI="=="boe-install-dir"/defaultodbc.iniExport ODBCINI

Note:DEFAULT_ODBCFILE can point to any file which holds the connection detailsfor the branded drivers.

4. Source the env.sh file.5. Configure the datasource in the defaultodbc.ini file, for example:

[ODBC Data Sources]sql2005=DataDirect 5.3 SQLServer Wire Protocol Driver

[sql2005]Driver=/export/home3/cs01/JupiterSP5/bobje/enterprise115/solaris_sparc/odbc/lib/CRmsss23.soDescription=DataDirect 5.3 SQLServer Wire Protocol DriverAddress=10.6.61.197,1433Database=bodb01QuotedId=YesAnsiNPW=NoLogonID=evalkitQEWSD=2454745Password=evalkit

6. Start the servers from the CMS.

The following is an excerpt of the default odbc.sbo file.

Example:

<DataBases><DataBase Active="Yes" Name="MS SQL Server 2005">



<Libraries>...</Libraries><Parameter Name="Family">Microsoft</Parameter>...<Parameter Name="Use DataDirect OEM Driver" Plat

form="Unix">No</Parameter>...</DataBase></DataBases>

Viewing DataDirect branded driver traces

After you activate the Connection Server trace, you are able to check thedriver you are using is DataDirect branded. The following is the trace log youobtain:

2008/10/06 15:24:22.663|<<| | | 9540| 1| ||||||||||||||||ODBC|MSSQL Server 2005|JobId:691948|ENTER SQLSetConnectAttr

SQLHDBC 0x0013b860SQLINTEGER 1041SQLPOINTER 0x0013bad0SQLINTEGER -3

2008/10/06 15:24:22.663|<<| | | 9540| 1| ||||||||||||||||ODBC|MSSQL Server 2005|JobId:691948|EXIT SQLSetConnectAttr with returncode 0 (SQL_SUCCESS)

SQLHDBC 0x0013b860SQLINTEGER 1041SQLPOINTER 0x0013bad0SQLINTEGER -3

2008/10/06 15:24:22.663|<<| | | 9540| 1| ||||||||||||||||ODBC|MSSQL Server 2005|JobId:691948|ENTER SQLSetConnectAttr

SQLHDBC 0x0013b860SQLINTEGER 1042SQLPOINTER 0x00179e88SQLINTEGER -3

2008/10/06 15:24:22.664|<<| | | 9540| 1| ||||||||||||||||ODBC|MSSQL Server 2005|JobId:691948|EXIT SQLSetConnectAttr with returncode 0 (SQL_SUCCESS)

SQLHDBC 0x0013b860SQLINTEGER 1042SQLPOINTER 0x00179e88SQLINTEGER -3

You identify the DataDirect branded driver to the 1041 and 1042 values ofSQLINTEGER that follow the two entries of SQLSetConnectAttr function.



Related Topics• To activate jobs and driver traces on page 36

Redbrick middleware

On Microsoft Windows, configure the middleware through the ODBC DataSource Administrator.



export RB_CONFIG=/usr/local/BD/Redbrick_6.20.UC5.USexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$RB_CONFIG/lib


DRIVER=/usr/local/BD/Redbrick_6.20.UC5.US/lib/rbodbcdrv.soSERVER=10.6.61.197:5050RB_CONFIG=/usr/u/user-name/RedBrickSDK6.20DATABASE=bodb01UID=evalkitPWD=evalkit

Test the connection with the RISQL tool, as follows:

risql -s datasource-name -h host-name -d database-nameuser-name password

Sybase ASE middleware

The Sybase ASE middleware is accessible through a native API.

Note:Before installing the middleware, create a JAVA_COMPILER environmentvariable set to NONE.

To configure a connection, use the Sybase Dsedit tool. To configure themiddleware in another character set than English, set LANG and LC_ALLvariables to the value you want.



Sybase ASE 15 middleware

On UNIX:1. Configure the environment by editing .bash_profile, for example:

export SYBASE=/usr/local/BD/sybase12.5export SYBASE_OCS=OCS-12_5export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SYBASE/OCS-12_5/devlib:$SYBASE/OCS-12_5/libexport PATH=$SYBASE/$SYBASE_OCS/bin:$PATH

2. Add the following details to the interfaces file, which is located in the/usr/local/BD/sybase12.5 directory:

[sybase15]master tcp ether 172.25.70.185 5000query tcp ether 172.25.70.185 5000

3. Use the isql tool that comes with the Sybase middleware to test theconnectivity, for example:

Isql -S host-name -D database-name -U username -P password

Sybase IQ middleware

The Sybase IQ middleware is accessible through an ODBC connectivity.

On Microsoft Windows, install the ODBC client driver and create yourdatasource.

On UNIX, create the datasource as follows:1. Configure the environment by editing .bash_profile, for example:

export ASDIR=/export/user-name/ODBCTest/sybase/ASIQ-12_7-odbcexport PATH=$PATH:$ASDIR/binexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ASDIR/lib


[ODBC Data Sources]SybaseIQ= Sybase IQ ODBC driver

[SybaseIQ]Driver=/usr/u/user-name/ODBCTest/ASIQ-12_7-odbc/libdbod



bc9_r.soDescription=Sybase Asiq12.7 host-nameDatabase=bodb01LogonID=arqc1Password=arqc1ServerName=iq127CommLinks=tcpip(host=host-name:2638)

To test the connectivity, you use the dbisqlc tool, which comes with theSybase IQ middleware. Run the following command either on MicrosoftWindows or UNIX:

dbisqlc -c 'uid=arqc1;pwd=arqc1;dbn=bodb01;eng=iq127;links=tcpip{host=10.6.61.73;port=2638}'

Teradata middleware

The following section describes how to configure the Teradata middleware.Teradata ODBC driver comes with a DataDirect driver manager.

1. First install the following programs:• Shared common components for Internationalization for Teradata

(TDICU)• Teradata GSS client package (TeraGSS)

You must install these programs before installing Teradata tools.

Note:If the following error message displays when installing TeraGSS, "Error1606. Could not access network location", run the workaroundthat you can find at http://support.microsoft.com/kb/315352. On MicrosoftWindows, do not forget to also install Microsoft Data Access Components(MDAC).

2. Install Teradata Tools and Utilities (TTU).

It is available for Microsoft Windows or UNIX with middleware versionsgreater than 3.4.

3. Install Teradata middleware.4. Do one of the following:

• Configure Teradata middleware from the ODBC Data SourceAdministrator on Microsoft Windows.



http://support.microsoft.com/kb/315352

• On UNIX, create the datasource as follows:a. Configure the environment by editing .bash_profile, for example:

export TERADATA_HOME=/usr/odbcexport LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TERADATA_HOME/lib:$TERADATA_HOME/driversexport PATH=$TERADATA_HOME/bin:$PATHexport TD_ICU_DATA=/opt/teradata/tdicu/lib

b. Configure the datasource by editing the odbc.ini file:

[ODBC Data Sources]TeraSFR=SFR DB

[TeraSFR]Driver=/usr/u/user-name/ODBCTest/drivers/tdata.soDescription=SFR DBDBCName=10.11.249.1LastUser=Username=Password=Database=DefaultDatabase=DontUseHelpDatabase=YesRunInQuietMode=Yes

Note:The example shows that the quiet mode is selected and the help databasefeature is not used. Selecting these options can avoid potential issues.

5. To force the character set of the middleware, add the characterSetparameter as follows:

CharacterSet=UTF8CharacterSet=ASCII (on Windows) or ISO-8859-1 (on UNIX)CharacterSet=LATIN9_0ACharacterSet=Shift-JIS

Note:Data is usually stored in Unicode in a Teradata database. So, you mustmake sure a conversion tool comes with the database if you want to useanother character set.

6. To test the connectivity, you use the Ad Hoc query tool that comes withthe Teradata middleware and located in the /usr/odbc/samples/C++installation directory on UNIX.



Related Topics• Miscellaneous checks on page 45



Tracing Connection Server

3

Activating Connection Server tracesAs Connection Server is embedded into the caller, both traces fromapplication and Connection Server are merged into one log file. For example,you find Connection Server traces in the designer_<pid>_<timestamp>_trace .log file.

To activate Connection Server traces, you must first edit the cs.cfg file. Thefollowing is the section of the file you need to modify:

<Traces Active="No"><Logger Implementation="C" ClassID="csTRACELOG"><Logger Implementation="Java" ClassID="com.businessobjects.connectionserver.logging.BOLogger"/><Trace Name="JobLevel" Active="Yes"><Trace Name="Job" Active="Yes"/></Trace><Trace Name="MiddleWare" Active="Yes"><Trace Name="Oracle" Active="Yes"/><Trace Name="Sybase" Active="Yes"/><Trace Name="Informix" Active="Yes"/><Trace Name="Teradata" Active="Yes"/><Trace Name="DB2" Active="Yes"/><Trace Name="DB2/iSeries" Active="Yes"/><Trace Name="ODBC2" Active="Yes"/><Trace Name="ODBC3" Active="Yes"/><Trace Name="OLEDB" Active="Yes"/><Trace Name="SAP BAPI" Active="Yes"/><Trace Name="OLE DB OLAP" Active="Yes"/><Trace Name="Essbase" Active="Yes"/></Trace></Traces>

To trace an application separately, copy the BO_Trace.ini file and renameit using the executable-file-name_Trace.ini pattern. For example:• Designer_Trace.ini for Designer• busobj_Trace.ini for Desktop Intelligence

To trace the other BOE servers, copy the BO_Trace.ini file in theBusinessObjects Enterprise 12.0\Logging folder.


Tracing Connection Server3 Activating Connection Server traces

To activate traces of Connection Server in librarymode

Connection Server is deployed in library mode when used with applicationssuch as Designer, Desktop Intelligence, and Web Intelligence.

1. Open the cs.cfg file and locate the Traces section.2. Set Active attribute of Traces element to Yes.3. Create and set values to the following environment variables:

• BO_TRACE_LOGDIR to set the folder name for logs, for examplec:\BOTraces.

• BO_TRACE_CONFIGDIR to set the folder name of configuration files forlogs, for example c:\BOTraces\config.

• BO_TRACE_CONFIGFILE to set the name of the configuration file, forexample BO_Trace.ini.

4. Create the BO_Trace.ini configuration file with this content:

active = true;importance = '<<';size = 100000;keep = false;

Note:The INI file name is case-sensitive.

5. Restart the client application.

Trace log files for Connection Server in library mode appear in the folderspecified with BO_TRACE_LOGDIR. These can be for example:

• designer_<pid>_<timestamp>_trace.log for Designer• busobj_<pid>_<timestamp>_trace.log for Desktop Intelligence• wireportserver_<pid>_<timestamp>_trace.log for Web Intelligence

To activate traces of Connection Server in servermode

Connection Server is deployed in server mode when used with DesktopInteligence in ZABO mode and Web Intelligence Rich Client applications.


3Tracing Connection ServerActivating Connection Server traces

1. Open the cs.cfg file and locate the Traces section.2. Set Active attribute of Traces element to Yes.3. Create and set values to the following environment variables:

• BO_TRACE_LOGDIR to set the folder name for logs, for examplec:\BOTraces.

• BO_TRACE_CONFIGDIR to set the folder name of configuration files forlogs, for example c:\BOTraces\config.

• BO_TRACE_CONFIGFILE to set the name of the configuration file, forexample BO_Trace.ini.

4. Create the BO_Trace.ini configuration file with this content:

active = true;importance = '<<';size = 100000;keep = false;

Note:The INI file name is case-sensitive.

5. Log into the BOE Central Management Console.6. Click Servers.7. Double-click Connection Server.8. In the Properties page, select Enable Execution Traces.9. Click Save & Close.10. Restart the client application.

Trace log files for Connection Server in server mode appear in the folderspecified with BO_TRACE_LOGDIR.

The following log files are generated:

• Setup and registration logs, which contain the plugin registration traces.

Connection Server relies on the cs_corba_plugin and cs_http_plugin.

• Client-side logs

When Connection Server relies on a CORBA proxy, the relevant log fileis the client log file. When Connection Server relies on HTTP proxy, therelevant log is the HTTP daemon log file.

• Server-side logs

A log file is generated for each running Connection Server process.



The log files can be as follows:

• ConnectionServer_<pid>_<timestamp>_trace.log

To activate traces of Java connectivities

You can enable traces for JDBC connectivities and JavaBean API. TheConnection Server tracing process, which is implemented by the com.businessobjects.connectionserver.logging package, relies on theBusinessObjects standard framework for logging, that is com.businessobjects.foundation.logging.

Note:You cannot trace Java connectivities in Titan release. This functionality isonly available in Connection Server Component 2.0 version (Mira).

1. Add the log4j.jar and logging.jar directory paths to the CLASSPATHenvironment variable, that can be for example: c:\BOTraces\lib\log4j.jar and c:\BOTraces\lib\logging.jar.

2. Copy the log4j.properties file in the directory that contains configuration files for logs, for example c:\BOTraces\config\META-INF\BusinessObjects.Logging\log4j.The file is as follows:

### file appenderlog4j.appender.file=org.apache.log4j.RollingFileAppenderlog4j.appender.file.maxFileSize=100KBlog4j.appender.file.maxBackupIndex=5log4j.appender.file.File=c://botrace//jdbc.loglog4j.appender.file.layout=org.apache.log4j.PatternLayoutlog4j.appender.file.layout.ConversionPattern=%d{ABSOLUTE}%5p %c{1}:%L - %m%nlog4j.rootLogger=ALL, file

3. Add the log4j.properties directory path to the CLASSPATH environmentvariable, that is, for example : c:\BOTraces\config.

To trace Java connectivities with another framework

You can use another logging framework to trace the Java connectivities.Available frameworks are the following:


3Tracing Connection ServerActivating Connection Server traces

• implementation of the standard logging framework based on com.businessobjects.connectionserver.logging.StandardLogging

• any implementation based on com.businessobjects.connectionserver.logging.Logger

1. Open the cs.cfg file and locate the Traces section.2. Modify the Logger element for Java implementation with a new ClassID

value.

Note:

If the META-INF/BusinessObjects.properties/ConnectionServer.loggerresource is defined, it takes precedence over the cs.cfg settings. Theresource must define a class implementing the Logger package.

You can also set an environment variable to a class that implements theLogger framework. The value set takes precedence over others ones.

To activate jobs and driver traces

You can enable traces for Jobs and drivers separately from application logsby editing the cs.cfg file. You can also select the driver you want to traceto isolate a problem.

1. Open the cs.cfg file and locate the Traces section.2. To activate Jobs traces, set Active attribute of Job and JobLevel

parameters to Yes.3. To activate driver traces, set Active attribute of the Middleware

parameter to Yes.4. To activate traces for a specific driver, set Active attribute of the driver

you want to trace to Yes.

To activate traces of OLAP connectivities

You can enable the following traces for OLAP connectivities:

• Connection Server traces for OLAP drivers.

Configuration is available for the SAP BAPI, OLE DB OLAP and EssbaseOLAP drivers in the cs.cfg file.



• MDA and SOFA traces.

The MDA and SOFA layers provide their own traces. MDA is the OLAPconnectivity used by Titan version and higher of Connection Server. Youmust provide the MDA team with MDA tracing information if an erroroccurred. SOFA is the OLAP connectivity used by previous versions ofConnection Server, Jupiter included.

Do the following:

1. Activate Connection Server traces.2. To trace the SOFA activity, run the pablo_sofa.reg file and restart your

system.This generates the sofa.log file.

3. To trace the MDA activity, run the Mda_log.reg file and restart yoursystem.This generates the mda.log file.

Note:You can find the registration entries files in the Knowledge Base/Titanfolder of the Data Access SharePoint site, at the following address:http://pgcentral.businessobjects.com/teamsites/Data%20Access/default.aspx.

Related Topics• Activating Connection Server traces on page 32

Reading Connection Server tracesThe following is an excerpt of a BOE trace:

2006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||unknown|unknown|JobId:0| ENTER SQLAllocHandleSQLSMALLINT 1SQLHANDLE 0x00000000SQLHANDLE * 0x0012F3602006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||unknown|unknown|JobId:0| EXIT SQLAllocHandle with return code 0(SQL_SUCCESS)

SQLSMALLINT 1SQLHANDLE 0x00000000SQLHANDLE * 0x0012F360

2006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||unknown|unknown|JobId:0| ENTER SQLSetEnvAttr

SQLHENV 0x02E012A0


3Tracing Connection ServerReading Connection Server traces

http://pgcentral.businessobjects.com/teamsites/Data%20Access/default.aspx

http://pgcentral.businessobjects.com/teamsites/Data%20Access/default.aspx

SQLINTEGER 200SQLPOINTER 0x00000003SQLINTEGER -6

2006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||unknown|unknown|JobId:0| EXIT SQLSetEnvAttr with return code 0(SQL_SUCCESS)

SQLHENV 0x02E012A0SQLINTEGER 200SQLPOINTER 0x00000003SQLINTEGER -6

2006/11/14 10:49:49.600|<<|||5784|5852|||||||||||||||||Teradata|Teradata V2 R5|JobId:25194648| ENTER SQLConnect

SQLHDBC 0x02E01348SQLTCHAR * 0x0183B564 [Tera_sean]SQLSMALLINT -3SQLTCHAR * 0x0183DA54 [csdev2]SQLSMALLINT -3SQLTCHAR * 0x0183DA34 [******]SQLSMALLINT -3

2006/11/14 10:50:01.820|<<|||5784|5852|||||||||||||||||Teradata|Teradata V2 R5|JobId:25194648| EXIT SQLConnect with returncode 0 (SQL_SUCCESS)

SQLHDBC 0x02E01348SQLTCHAR * 0x0183B564 [Tera_sean]SQLSMALLINT -3SQLTCHAR * 0x0183DA54 [csdev2]SQLSMALLINT -3SQLTCHAR * 0x0183DA34 [******]SQLSMALLINT -3

ENTER traces identify the middleware API call, while EXIT traces identify thereturned call. Each function has its own trace.

Traces help you find the following:• Call expections, if |E| is displayed.• API errors, if the return code -1 is displayed.• An error message if the middleware API fails.• No returned call from a middleware API, if there is no EXIT after ENTER.

Activating ODBC tracesIn the event your environment uses an ODBC connectivity, you can alsoactivate ODBC traces to facilitate your understanding of the current problem.

On Microsoft Windows:1. Make sure any ODBC consuming programs are running.2. Open the "ODBC Data Source Administrator" and click the Tracing tab.


Tracing Connection Server3 Activating ODBC traces

3. Edit Log File Path and Custom Trace DLL.4. Click Start Tracing Now.

Note:Close and reopen the dialog box to verify that your modifications havebeen saved.

On UNIX, the way you activate traces depends on the ODBC manager youuse. For Teradata, edit the ODBC section of the odbc.ini file as follows:

[ODBC]InstallDir=/usr/u/user-name/ODBCTest/teradata/Teradata3.04.00.00Trace=1TraceDll=/usr/u/user-name/ODBCTest/teradata/Teradata3.04.00.00/lib/odbctrac.soTraceFile=/usr/u/user-name/ODBCTest/odbctrace.logTraceAutoStop=0


3Tracing Connection ServerActivating ODBC traces


Tracing Connection Server3 Activating ODBC traces

Investigating errors

4

To avoid connection failures at startupSince Component 2.0 release (Mira), Connection Server in server modealways loads all data access drivers on startup. You may encounterconnection failures at startup if the middleware involved is not configuredcorrectly.

• To avoid Connection Server failures at startup, do one of the following:• when installing the BusinessObjects Enterprise suite, select a custom

installation and specify the connectivities you want to deploy for eachtype of database you require.

• when configuring Connection Server in the cs.cfg file, specify thedrivers you want to load in the <ActiveDataSources> section of theserver mode.

You must follow these instructions for both patch or full installation ofBusinessObjects Enterprise suite.

Example:

...<Server><Parameter Name="Load Drivers On Startup">Yes</Parameter><Parameter Name="Max Pool Time">60</Parameter><Parameter Name="Transient Object Timeout">60</Parameter><ActiveDataSources><NetworkLayer Name="ODBC"><DataBase Name="MS SQL Server.*$"/></NetworkLayer><NetworkLayer Name="Oracle OCI"><DataBase Name="Oracle 9"/><DataBase Name="Oracle 8"/></NetworkLayer></ActiveDataSources></Server>...

Note:For more information about configuring Connection Server, refer to the DataAccess Guide.


Investigating errors4 To avoid connection failures at startup

To debug Connection Server at startupYou usually debug Connection Server while it runs. However, you may needto solve a problem that occurs at Connection Server startup.

1. Open the Central Management Console.2. Locate the Central Management Server.3. Click Properties.4. Add -disablehostauth to the CMS command line.

5. Restart the CMS.6. Stop Connection Server.7. Restart Connection Server using the following command line parameters:

-fg -name yourhostname.ConnectionServer -ns cmshostname:port.These are the minimal set of flags required to run a new instance ofConnection Server.

Note:Any stdout/stderr output will be displayed in the console.


4Investigating errorsTo debug Connection Server at startup

General diagnosisThe following example shows one of the most common errors you can facewhen trying to access data through Connection Server.

When you create or edit a connection in Designer, you can test if it is valid.The workflow is the following:

1. Start Designer.2. Start New Connection wizard.3. Click Test Connection.

The following error message displays: Server is not responding.

The following sections provide you with actions you need to take first whenfacing an error.

To check your system before further investigations

First do the following verifications before any deeper investigation:

1. Click on the Details >> button to display the message.


Investigating errors4 General diagnosis

If it contains information about the connectivity, the error may be causedby the middleware or the database.

2. Check the Internet for details if the detailed error message containstechnical information such as an ORA- report number.

3. Check connectivities by using middleware tools such as SQL*Plus,ODBCTest and WinSQL.On UNIX, use tnsping utility to check Oracle connectivity.

4. If the connectivity test is successful, check connection on ConnectionServer side by using the cscheck tool.

5. If cscheck fails, check the Connection Server driver components.6. Check the data access driver is exposed correctly in your environment.7. Check driver configuration in SBO and COD configuration files.

Usually, you must not modify configuration files of ODBC drivers. Revertto default ones if you have modify them.

8. Activate traces of Connection Server and middleware processes to providedevelopers in charge of fixing bugs with traces obtained when runningworkflows that failed.

Note:For more information about the cscheck tool, refer to the Connection Servertesting guide.

Related Topics• Configuring middleware on page 10• Activating Connection Server traces on page 32

Miscellaneous checks

This section presents supplementary checks you can do before any furtherinvestigation. Some of the following address specific datasources anddeployments.

Checking library registration

Make sure the Connection Server DLLs have been correctly registered inyour operating system during the BOE installation.


4Investigating errorsGeneral diagnosis

Checking JVM implementation

The Linux, Sun Solaris and Microsoft Windows operating systems use thesame JVM implementation, while HP-UX and AIX use a different one. Checkit as a potential source of errors for JDBC connections.

Checking JVM configuration

The <JavaVM> parent element of cs.cfg file specifies the default library ofthe Java Virtual Machine (JVM) used by the data access layer. Check theconfiguration and see if it fits your requirements. If it does not, you can dothe following:

• overwrite the default JVM library value in <LibraryName> child element

Note:Make sure you set an absolute path to the JVM library directory.

• setting specific options by adding an <Options> child element

Caution:You must be aware that adding JVM options may create bad side effects.

Example:

The example illustrates the following changes made in the configuration ofthe JVM:

• a new JVM library set with its directory path• an option that sets the maximum memory size allocated to the JVM to 1024

MB. This can potentially solve out of memory issues in JDBC connections.

...<JavaVM><LibraryName JNIVersion="JNI_VERSION_1_4">absolute-path/jvm.dll</LibraryName><Options><Option>-Xmx1024m</Option></Options></JavaVM>



Checking JDBC driver configuration• Make sure you set <ClassPath> element of jdbc.sbo file correctly. Verify

the validity of the file against the DTD by using an XML editor such asAltova XMLSpy.

• Make sure you write driver URL and java class names in the jdbc.sbofile correctly, especially if the driver you use is not the one provided bythe database vendor.

Checking Teradata connectivity

Make sure you select the following ODBC driver options for Teradata:• no HELP DATABASE• Run in Quiet Mode

You select these options in the ODBC Data Source Administrator on MicrosoftWindows or you specify them in the odbc.ini file on UNIX.

Complex deployment case

If the BOE architecture you are using consists of different Connection Serverstacks, that is Connection Servers installed on different machines workingas a cluster and connected to different databases, you must make sure allthe configurations of Connection Servers are identical. This is only true forJupiter and Titan releases.

In the Component 2.0 version (Mira), you can configure Connection Serversto access different datasources.

Note:For more information about how to set specific datasources to ConnectionServer, refer to “Configuring the driver filter” in the Data Access Guide.

Checking Data Federator configuration

The following case relates to an architecture involving an ODBC connection,as implemented by an OpenAccess ODBC driver, between Data FederatorQuery Server and Connection Server. To avoid connection errors from aBOE application, make sure you configure openrda.ini and cs.cfg filescorrectly.

Note:For more information about how to configure Connection Server and DataFederator Query Server, refer to the Data Access Guide.


4Investigating errorsGeneral diagnosis

Related Topics• Teradata middleware on page 28

To do a first diagnostics on Microsoft Windows

If BOE is installed on Microsoft Windows, do the following to do a firstdiagnostics:

1. Check dependencies between the Connection Server DLL files by usingthe Dependency Walker tool.

2. Check the PATH environment variable contains the paths to the appropriateDLLs.

3. Check if you have set environment variables demanded by databasescorrectly.For example, check if TS_ADMIN environment variable, which is neededby the Oracle database, is set correctly.

Related Topics• Configuring middleware on page 10

To do a first diagnostics on UNIX

If BOE is installed on a UNIX machine, do the following to establish a firstdiagnostics:

1. Check paths of the Connection Server library files:a. Execute the following command in the bash shell to source a build

environment script:

source env.sh

b. Execute the following command to list the .so files on which dependthe following file, and find out any dependency problem:

ldd <driver_name>.so

Note:Make sure you have the read/write rights for .so files and theirdirectories. Make also sure that the symbolic links you may havecreated on these files are not broken.



c. Modify the library variable to fix your dependency problems.

2. Check if you provide correct driver managers to your working drivers.3. Check if you have set environment variables required by databases

correctly.For example, TNS_ADMIN, which is needed by the Oracle database, mustcontain a path to the tnsnames.ora file. Also set ORACLE_HOME to theinstallation directory path, and ODBCINI to the odbc.ini file directorypath.

Related Topics• Configuring middleware on page 10• Selecting a driver manager on UNIX on page 49

Investigating further

The problem may not be a connection failure. Depending on the type of errorand its severity, you may need to answer the following questions:

• Does the problem occur on any kind of operating systems (MicrosoftWindows, UNIX, and Linux)?

• Does the problem occur with any kind of database and connectivity (Oracleand non-Oracle, ODBC)?

• Does the problem occur in all Connection Server modes (library, CORBA,and HTTP)?

• Does the problem occur with any BOE application (Desktop Intelligence,Web Intelligence, ZABO mode)?

• Does the same problem occur with a query and a stored procedure?• Does the problem occur when the same SQL statement is tested through

another SQL tool like WinSQL?

Selecting a driver manager on UNIXThe Microsoft Windows operating system comes with a standard ODBCdriver manager. In a UNIX environment, there is no standard way to managethe driver manager. To connect a database on UNIX by using an ODBCconnectivity, you must use the driver manager that is provided by thedatabase vendor, along with the ODBC driver that is also provided. Somevendors offer the following solutions:


4Investigating errorsSelecting a driver manager on UNIX

• DataDirect driver manager, which is a licensed product.• unixODBC driver manager, which is an open source project.• Other vendors provide a specific ODBC driver manager with their

middleware.

Connection Server allows you to use:

• in most cases, the DataDirect driver manager that comes with the driverprovided by the database.

• for the MySQL database, the unixODBC driver manager that comes withthe MySQL ODBC driver.

The following is an excerpt of the odbc.sbo file that Connection Serverprovides for configuring ODBC drivers:

<DataBases><DataBase Active="Yes" Name="Generic ODBC datasource"><Libraries><Library Platform="MSWindows">dbd_wodbc</Library><Library Platform="MSWindows">dbd_odbc</Library><Library Platform="Unix">dbd_wddodbc</Library><Library Platform="Unix">dbd_ddodbc</Library></Libraries><Parameter Name="CharSet Table" Platform="Unix">datadirect</Pa

rameter>...</DataBases>

This means that Connection Server in library mode uses the generic ODBCdriver with the DataDirect driver manager in the UNIX configuration, as statedby wdd, which stands for Unicode DataDirect and dd, which stands for ASCIIDataDirect. If you want to use unixODBC driver manager, comment outprevious two rows and uncomment one of the last two rows, where wuxstands for Unicode unixODBC and ux for ASCII unixODBC. Make sure youput the row you uncomment on top of the section, because of the readingorder of the file. In this last case, you also need to comment out the <Parameter name="CharSet Table" Platform="Unix"> element.

Note:Problems of incompability with drivers may occur when using more than oneODBC datasource on UNIX, if these use different versions of driver managers.


Investigating errors4 Selecting a driver manager on UNIX

IndexAaudience of the guide 6

Bbranded drivers 22

CCMS 43Connection Server

debugging at startup 42, 43traces 32tracing drivers 36tracing Java connectivities 35tracing jobs 36tracing library mode 33tracing OLAP connectivities 36tracing server mode 33

connections 44

DData Federator 45DataDirect driver manager 49DataDirect drivers 21, 22DB2 11diagnostics 44driver managers 49drivers

tracing 36

EEssbase 19

IInformix 12Ingres 13investigating errors 49

JJava connectivities 35Java traces 35Jupiter release 22, 36JVM 45

LLD_LIBRARY_PATH 10LIBPATH 10log files 33log4j logging framework 35

MMDA traces 36Microsoft Windows 48middleware

configuring 10DB2 Client Access 11DB2 UDB 11Informix 12Ingres 13


middleware (continued)MySQL 17Netezza 18OLAP 19OLE DB 20Oracle 20Redbrick 26SQL Server 21Sybase ASE 26Sybase IQ 27Teradata 28

Mira release 35, 42, 45MySQL 17

NNetezza 18no HELP DATABASE option 28, 45

OODBC

traces 38OLAP

middleware 19traces 36

OLE DB 20Oracle 20

RRedbrick 26registration 45requirements

users 6

Run in Quiet Mode option 28, 45

SSAP BW 19SHLIB_PATH 10SOFA traces 36SQL Server 21, 22Sybase 26, 27

TTeradata 28, 45Titan release 35, 36Titan SP2 release 22traces

activating BOE 32activating ODBC 38Java connectivities 35jobs and drivers 36library mode 33OLAP connectivities 36reading BOE 37server mode 33

UUNIX 48unixODBC driver manager 49user requirements 6

ZZABO 49


Index

Connection Server Troubleshooting Guide - … sysmaster ; select is_ansi, name from sysdatabases ;...

Documents

Transcript of Connection Server Troubleshooting Guide - … sysmaster ; select is_ansi, name from sysdatabases ;...