Siebel Server Start Up Errors After Migration Of DB2 Client To 10.5.5 when using DB2 CC: SBL-SRM-00016 and SBL-SEC-10018 (Doc ID 2069828.1)

Last updated on JULY 11, 2017

Applies to:

Siebel Financial Services CRM - Version 8.1.1.14 [IP2014] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.14.8 [IP2014] version, Installation

After migrating the DB2 client software from DB2 v9.7.4 to v10.5.5 (DB platform: IBM z/OS on System z), when attempting to start the Siebel Server
the following error occurs.
ERROR
-----------------------
We see login and security related errors (SBL-SEC-10001, SBL-SEC-10018, SBL-SRM-00016, SBL-SVR-03005,SBL-CSO-01013, SBL-ADM-09152,...).

The first error is on the SRBroker, where we have

GenericLog GenericError 1 0012d67056120014:0 2015-10-06 07:28:51 (srbthrd.cpp (4066) err=2097168 sys=0) SBL-SRM-00016: Kan de databaseomgeving Unable to start common api niet initialiseren
GenericLog GenericError 1 0012d67056120014:0 2015-10-06 07:28:51 (srbmtsrv.cpp (86) err=2097168 sys=0) SBL-SRM-00016: Kan de databaseomgeving Unable to start common api niet initialiseren

The following errors were found in the ServerMgr.log file:

SBL-SEC-10018: [IBM][CLI Driver][DB2] SQL0100W  No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table.  SQLSTATE=02000
SBL-SEC-10001: Binnen het subsysteem voor verificatie voor de Siebel-toepassing is een interne fout opgetreden. Neem contact op met de systeembeheerder.
Server Manager Authentication Failed -- unexpected failure within the security adapter manager, plug-in security adapter or underlying authentication system
SBL-CSO-01013: Intern: de SCC-context is niet geïnitialiseerd


We have checked the DB2 settings, paths, logs, etc.
We found out that when we switch off DB2 connection concentrator (DB2 CC) using the setting DB2CONNECT_IN_APP_PROCESS=YES, the Siebel environment starts properly.
When switching on DB2 CC (DB2CONNECT_IN_APP_PROCESS=NO), we have the errors and SRBroker does not start.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Switch on DB2 connection concentrator (also known as gateway mode) (DB2 CC) using the setting DB2CONNECT_IN_APP_PROCESS=NO
2. Start the Siebel Server


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot start the Siebel Server when DB2 connection concentrator (DB2 CC) is on.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms