SBL-CDM-00191: Unable to connect to ODBC datasource "%1" as user "%2."

Applies to:

Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2000 Server SP 2

This document was previously published as Siebel SR 38-3337584521.

Symptoms

In our production environment, as part of a release of new Forecasting functionality, we need to create a database schema kit for our remote users. This schema kit has continued to error with the message that SQLError    Statement    0    0    2007-04-28 06:53:45    SQL Statement:
drop index SIEBEL56.S_EVT_ACT_M10
DBCLog    DBCLogError    1    0    2007-04-28 06:53:45    [DataDirect][ODBC Oracle driver][Oracle]ORA-00054: resource busy and acquire with NOWAIT specified
The complete log file from one of these failed attempts is attached.
We found an SR from March with this same message, and the recommendation to perform this task at a quiet time. We have shutdown the application to disconnect any users, we have cancelled backups etc. We tried to run this late at night/early morning. We are now requesting that our service center bounce our database. We need your help to find a way to keep the Upgrade Kit builder from trying to rebuild indexes (where it doesn't need to do so) or to get this process to run somehow.

Solution

Message 1

For the benefit of other readers,

Problem: After upgraded from to 7.8.2.3 customer was not able perform schema upgrade kit and the process was failing with the error message below

Silverrod    Statement    0    0    2007-04-28 06:53:45    SQL Statement:
Drop index SIEBEL56.S_EVT_ACT_M10

Backlog    DBCLogError    1    0    2007-04-28 06:53:45    [DataDirect][ODBC Oracle driver][Oracle]ORA-00054: resource busy and acquire with NOWAIT specified

Error    1    0    2007-04-28 06:53:45    (kitwizsv.cpp (5043)) SBL-CDM-00190: Additional Error Message (from ODBC): [DataDirect][ODBC Oracle driver][Oracle]ORA-00054: resource busy and acquire with NOWAIT specified

- Customer tried to stop/restart siebel gateway, server, and oracle database server but did not help

Resolution:

Suggested customer DBA to start the oracle database instance into restricted mode only allowing SADMIN, the database owner and a couple of support personnel access, then shutdown down all the components except the below, For details refer Service Request #: 38-3067775581

Stop all Siebel Server components except:
   - File System Manager
   - Server Manager
   - Server Request Broker
   - Server Request Processor
   - Server Tables Cleanup
   - Siebel Connection Broker
   - Upgrade Kit Builder

The upgrade kit succeeded

Applies to:

Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] Life Sci
Database: Oracle 10.1.0.5
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: HP 9000 Series HP-UX

This document was previously published as Siebel SR 38-3299762327.

Symptoms

The Upgrade Kit Builder fails when trying to create database schema kit.

2021 2007-03-14 17:08:18 2007-03-14 17:08:29 -0400 00000178 001 003f 0001 09 UpgKitBldr 48372 1680 4132 e:\sea78\siebsrvr\log\UpgKitBldr_48372.log 7.8.2.3 [19221] ENU

SQLError Statement 0 0 2007-03-14 17:08:18 SQL Statement:
drop index siebel.S_SRM_REQUEST_M1

DBCLog DBCLogError 1 0 2007-03-14 17:08:18 [DataDirect][ODBC Oracle driver][Oracle]ORA-00054: resource busy and acquire with NOWAIT specified


ObjMgrLog Error 1 0 2007-03-14 17:08:18 (kitwizsv.cpp (5043)) SBL-CDM-00190: Additional Error Message (from ODBC): [DataDirect][ODBC Oracle driver][Oracle]ORA-00054: resource busy and acquire with NOWAIT specified


UpgKitBldrLog UpgKBError 1 0 2007-03-14 17:08:18 Error in callback of UTLDbDdlDbMerge: pOperCallback UTLDbDdlOperIndModify

UpgKitBldrLog UpgKBError 1 0 2007-03-14 17:08:18 Part 2 of 4: Error in merging dictionaries

Solution

Message 1

For benefit of the other readers.

With Oracle 9i or 10g, UpgKitBldr component for database schema kit recreates any index that has "DESC" key. This behavior is caused because Oracle 9i and 10g use FUNCTION-BASED index to achieve "DESC" key, while UpgKitBldr cannot detect this information correctly. Therefore UpgKitBldr mistakenly treats that index needs to be recreated. As a result, the same index is recreated again. In other words, the final outcome is fine as long as you run UpgKitBldr while system is not busy.

If you create database schema kit while database is in use, you may experience "ORA-00054: resource busy and acquire with NOWAIT specified". Please create database schema kit in off hour. Since UpgKitBldr does what it does not have to do, I have filed change request 12-1IR1S4K.


Thank you

Applies to:

Siebel Marketing - Version: 10.1.3.4.0 [1900] - Release: 10g

Information in this document applies to any platform.
While the user is trying to create a Target List, the following error is coming up:

Unable to connect to ODBC datasource "Analytics Web" as user "SINHAMAH."(SBL-CDM-00191)

However please note that the behavior is very erratic and does not occur all the time. Sometimes it starts working also.
For all the time, we are using the same set of data to create the Target List.

The system uses SSO to login into the application.

Goal

The successful creation of Target List.

Solution

In the problematic enviroment, it was identified the following scenario:

The OBI Server and OBI Web was in the machine (say Machine A)

The OBI ODBC Client exists in different machines (say B,C,D,....)

It was identified that there were some discrepancy in mentioning the "DSN" in the above machines. For Ex., in some of above machine, the DSN was mentioned as "Analytics Web" (a space in between Analytics and Web) whereas in other machines the DSN was mentioned as "AnalyticsWeb" (no space between Analytics and Web).

Upon setting all the parameters (like ODBC DSN, etc) matching with each other, it worked fine.

Applies to:

Product Release: V7 (Professional)
Version: 7.7.2.4 [18365]
Database: Oracle 9.2.0.7
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3198154191.

Symptoms

SBL-CDM-00191, SBL-OMS-00203

Hi,

I'm attempting to create a database schema upgrade kit however the logs are showing there is an 'Error in connecting via ODBC as Database User: sadmin'.

I'm using a thick client and have tried supplying our actual SADMIN password, and just 'SADMIN' as the password.

Validity of ODBC connection has been confirmed via Test Connection facility in ODBC administrator.

A search of SupportWeb doesn't yield too many SRs reporting similar issues however I did follow the advice in Alert 559.

Logs are attached for your review (Generic Log and Trace Log levels increased to 4 for UpgKitBldr comp).

Thanks & Regards,

John

Solution

Message 1

For the benefit of other users:

Problem:

see description

Resolution:

When creating the DB Upgrade Kit, customer had to enter the ODBC Data source. This has been set to EXCH.BPTREXT1.BIAM.IE. (ODBC Datasource from Mobile Web Client machine)

This is not correct, customer has to set it to the ODBC Data source used in the siebel server hosting the UpgradeKitBuilder Component.

Runing the Upgrade KIt once again and settin the ODBC Data source to the apprioriate value as described above solved the reported behavior.


Thanks and Regards,

Oracle Product Support

Key Words: DB Upgrade Kit, ODBC