After using the DB2 Table Definer to view a DB2 table definition, subsequent DB2 table accesses use the wrong SERVERID.

After using the DB2 Table Definer to view a DB2 table definition, subsequent DB2 table accesses use the wrong SERVERID.

book

Article ID: KB0094441

calendar_today

Updated On:

Products Versions
TIBCO Service Gateway for DB2 -
Not Applicable -

Description

Resolution:
This error occurs when the site is using two or more DB2 gateways with different SERVERIDs within an Object Service Broker configuration. If the client logs on to the TIBCO Object Service Broker (OSB) workbench and using the OSB Table Definer for DB2 views the definition for DB2 table1 which has SERVERID=loc1 specified, the SERVERID specified for this table is cached. If the client then exits the OSB DB2 Table Definer workbench and tries to BROWSE DB2 table2 which has a SERVERID=loc2 value defined the SERVERID cached by the Table Definer is used in error. The access fails because the request is sent to SERVERID=loc1 which is incorrect for DB2 table2.


Environment:
============
* TIBCO Service Gateway™ for DB2
* multiple SERVERIDs are used for two or more DB2 gateway servers
* the client uses the OSB DB2 Table Definer prior to accessing other DB2 tables

Symptoms:
=========
DB2 table access routed to the wrong DB2 gateway server after the TIBCO Object Server Broker Table Definer is used to view a DB2 Table Definition.

Cause:
======
Due to a programming error, when viewing a DB2 table definition with the TIBCO Object Service Broker DB2 Table Definer, the SERVERID information is stored internally within the Execution Environment. When a different DB2 table is accessed through the session, the previously cached SERVERID value is used from the Table Definer operation rather than the correct SERVERID defined for the subsequent DB2 table(s). This error is caused by the Table Definer setting a dynamic server parm for table1 and never clearing the information when the Table Definer terminates.

Resolution:
===========
Users experiencing this problem should open a service request with TIBCO Support and request notification when the fix for problem report OSBZ-1467 is available.

Workaround:
===========
When using the TIBCO Object Service Broker Table Definer for DB2 tables, logoff the Execution Environment and then reconnect before trying to access any other DB2 tables if you are using more than one DB2 gateway SERVERID for your Object Service Broker system. This will clear the cached SERVERID information and allow normal access to other DB2 databases.

References:
===========
OSBZ-1467
TIBCO Service Gateway™ for DB2 Installing and Operating

Issue/Introduction

After using the DB2 Table Definer to view a DB2 table definition, subsequent DB2 table accesses use the wrong SERVERID.