This site has been specifically designed to troubleshoot all Siebel related issues. When any exception or error occurs in Siebel, the cause is given by a specific error code. Whenever we face an issue, we try to Google or search for a resolution mostly from Oracle Support, IT Toolbox, Siebel Unleashed etc. I have tried to search for all the solutions for a particular error code in all the mentioned sites and put all the solutions in this site.

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.

- 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

Solution

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:

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.