siebel-error

Thursday, February 24, 2011

SBL-DBC-00107: An Oracle database error has occurred.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

EAI OM, Loyalty Engine Component Failure occur multiple times.

(oracon.cpp (3246)) SBL-DBC-00107: An Oracle database error has occurred.
Please continue or ask your systems administrator to check your application configuration if the problem persists.

(secmgr.cpp (2679) err=4597538 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

Cause

Siebel component shows error:

(SBL-DBC-00107)ORA-00257: archiver error. Connect internal only, until freed.

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

Solution

The error is caused by the fact that the archiver process is unable to archive the current online redolog due to lack of space in the destination for the archivelogs.

- Best option is to make more space available in the archive log destination (log_archive_dest_n).

- Increased frequency of log purges.
Work with your DBA to address the above.

- Restart Siebel servers.

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Cause

Solution

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Cause

Solution

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Cause

Solution

Applies to:

Siebel Server Manager - Version: 8.1.1.2 SIA[21215] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Cause

Solution

SBL-DBC-00106: An ODBC database error has occurred. Possibly the database name is invalid.

Show Bug Attributes

Bug Attributes

Type	B - Defect	Fixed in Product Version	0UNKNOWN
Severity	2 - Severe Loss of Service	Product Version	1.0
Status	30 - Additional Information Requested	Platform	289 - GENERIC (All Platforms)
Created	29-Jun-2007	Platform Version	NO DATA
Updated	12-Jan-2011	Base Bug	-
Database Version	9.2
Affects Platforms	Generic
Product Source	Oracle

Show Related Products

Related Products

Line	Siebel	Family	Customer Relationship Management
Area	CRM - Enterprise Edition	Product	8981 - Siebel Apps - Service

Hdr: 10527107 9.2 ASGN_MGR 1.0 SER_PRO PRODID-8981 PORTID-289
Abstract: [CR#12-1K216WF][FR#12-1K216XJ] CANNOT INVOKE LOAD SPLITER ON DEDICATED WEB CLIEN

*** 08/13/07 10:06 am ***
Summary: Cannot invoke Load Spliter on dedicated web client
How to Reproduce: Invoking Load Spliter on dedicated client failed with:
SQLTraceAll SQLTraceAll 4 0 2007-05-16 09:12:33 No DNS found
ObjMgrBusServiceLog Error 1 0 2007-05-16 09:12:33 (loadspltrsvc.cpp (567)) 
SBL-DBC-00106: An ODBC database error has occurred. Possibly the database 
name is invalid.

However it works fine in web client.

How to reproduce:
- Import attached BS into the client or even Siebel Tools
- Invoke it from client (e.g. using Business Service Simulator)

You will the above error message.

See also log file attached.
*** 08/13/07 10:06 am ***
*** 08/13/07 10:02 am ***
*** 01/06/11 12:32 pm *** (CHG: Pri->2)

SBL-DBC-00105: An error has occurred executing a Sql statement.

Applies to:

Siebel Tools - Version: 7.7.2 [18325] to 8.1.1.3[21219] [Release: to V8]
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: 7.7.2.1 [18353]

Database: Oracle 9.2.0.6

Application Server OS: Microsoft Windows 2003 Server

Database Server OS: Sun Solaris 9

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

"" Checked for Relevance on 17-SEP-2010 ""

Symptoms

SBL-DBC-00105

Customer created an external view on SIEBVIEW schema (v$activity_follow_ups_ebc) in order to join two types of Activity rows (SQL UNION) - old ones that have no parent activity reference, and new ones that have this reference. The view is working fine from SQL Navigator, and there are no errors in any type of direct SQL Queries that customer made.

An EBC has been created based on this view to display the date in a List Applet that was inserted on Acitivity List view.

When customer opens this view, the following error occur:
"An error has occurred executing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)".

If customer changes the view, and select only the new group of records, the EBC is working fine and he can see records from GUI. But if he puts in the view only OLD records, he is getting this error.

Cause

The customer's view definition for the External Business Component (EBC) included a restriction on a date:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
... act.created > '17-Sep-2001' -- to eliminate activities created before Siebel roll-out
...

The view could be accessed successfully from a third party tool, but a select statement generated from the Siebel Application caused an SQL error.

Solution

As the date formatting depends on the session's NLS (National Language Support) settings, we suggested an adapted version that would work independent from the current NLS setting:

CREATE OR REPLACE VIEW
...
AS SELECT
....
from siebel.s_evt_act act -- Activity
...
WHERE
act.created > (to_date('17.09.2001','DD.MM.YYYY'))

The customer changed the view definition accordingly and no more SQL errors occurred when accessing the EBC from the Siebel application.

Please note that the to_date function above and its syntax is specific to Oracle RDBMS.

Applies to:

Siebel Tools - Version: 8.0.0.2 [20412] and later   [Release: V8 and later ]
Siebel Tools - Version: 7.7.1 SIA [18306] to 8.0.0.2 [20412]   [Release: V7 to V8]
Siebel Tools - Version: 7.7.1 [18306] to 8.0.0.2 [20412]   [Release: V7 to V8]
Information in this document applies to any platform.

Symptoms

The customer created an External Business Component (EBC) based upon a database view on another application's tables (ERP - Oracle DB)

When querying the EBC using a simple Workflow Siebel Operation this resulted in the following warning message:

SBL-DBC-00105
--
ORA-24347: Warning of a NULL column in an aggregate function

which caused Siebel Error

SBL-DBC-00105

"An error has occurred executing a Sql statement.

Please continue or ask your systems administrator to check your application configuration if the problem persists."

then.

(Note that this behavior is generally independent from using a workflow or not for querying)

Cause

ORA-24347: Warning of a NULL column in an aggregate function

is a warning reported from the Oracle RDBMS when trying to use aggregation functions like SUM or AVG on records containing NULL values.

In this case, the customer's database view definition included a SUM:

create or replace view xx_ar_cust_ref_credit_sum_v as

select

addr.orig_system_reference orig_sys_ref_acct_id

...

sum(credit_data.overall_credit_limit) overall_credit_limit,

sum(credit_data.balance_due) balance_due
...

Solution

Changing the database view definition, using NVL to handle null values was suggested and confirmed to resolve this.

Please invoke Oracle Database Support or Consulting (billable) if you need assistance implementing this for your specific view definition.

Test your view definitions thoroughly before using them in a production environment to avoid database errors like this, and be aware that database views in EBCs cannot be used to update records (as the RDBMS will prevent updating records via database views).

http://www.dbasupport.com/forums/archive/index.php/t-17208.html

describes similar NULL value related errors and has examples using NVL - if this document should no longer exist

try searching for

ORA-24347 and NVL

on the Web.

References

NOTE:535155.1 - EBC generates ORA-24347 error

http://www.dbasupport.com/forums/archive/index.php/t-17208.html

Applies to:

Siebel System Software - Version: 7.7.2 [18325] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.7.2.6 [18372]

Database: Oracle 9.2.0.6

Application Server OS: Microsoft Windows 2000 Advanced Server SP 3

Database Server OS: IBM AIX 5L 5.1

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

Symptoms

Customer reported the following:

We have come across an error in our Siebel production environment when running a query.

The error message is,

"An error has occurred executing a Sql statement.

Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00105)

ORA-00600: internal error code, arguments: [qkabix], [0], []. [], []... "

I have referenced on the My Oracle Support, the Siebel Error Message information on SBL-DBC-00105.

I did the spooling, found the SQL causing problems and then I ran the SQL in sqlplus. The SQL ran fine without error.

One thing I did try was changing the InsensitivityFactor to 1 rather than 2. And this did resolve the problem.

Is the case insensitivity factor a valid reason for this error we see?

Is there anything else I can do to confirm the cause of this problem?

Solution

For the benefit of other readers:

Customer encountered ORA-600 [qkabix]

1. Is the case insensitivity factor a valid reason for this error we see?

-- No. Setting InsensitivityFactor may not be a permanent solution.

2. Is there anything else I can do to confirm the cause of this problem?

The ORA-600 error with qkabix should appear in Oracle alert and/or trace files when the query ran and return with error.

For further information on ORA-600 [qkabix], please do a search in Oracle metalink using “ORA-600 [qkabix]”. This error is reported when Oracle fails with rowid-to-bitmap conversion when running a select statement with lots of joins and tables involved. Possible workaround is to set "_B_TREE_BITMAP_PLANS" = false.

_B_TREE_BITMAP_PLANS enables creation of interim bitmap representation for tables in a query with only binary index(es). Default value is FALSE in Oracle 8i and TRUE in Oracle 9i or later.

Siebel should work with _B_TREE_BITMAP_PLANS = FALSE with no issues since Siebel has been tested with Oracle 8i – prior version. This is supported so please feel free to set this to false.

Applies to:

Siebel Tools - Version: 7.5.3 [16157] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.5.3 [16157]

Database: Oracle 9i

Application Server OS: Microsoft Windows 2000 Advanced Server SP 4

Database Server OS: Sun Solaris 8

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

""Checked for Relevance on 03-Dec-2010""

Symptoms

We have the business requirement to be able to search for all employees attached

to an activity without having to type "EXISTS" in the "Owned By" MVF. After setting the "Use

Primary Join" flag to "FALSE" for the Action/Employee MVL in BC Action, an SQL error occurs when

navigating to the Activities Screen.

Cause

The behavior described by the customer is reproducible using a standard Siebel environment. The steps are the following:

1. Using Siebel Tools set the 'Use Primary Join' property of the

'Employee' MVL to FALSE (Unchecked) in 'Action' BC. Compile the BC.

2. Launch Siebel Call Center application:

> The Home Page cannot be displayed and the following error occurs:

- - -

We detected an Error which may have occurred for one or more of the following reasons:

An error has occurred executing a Sql statement. Please continue or ask

your systems administrator to check your application configuration if

the problem persists.(SBL-DBC-00105)

- - -

NOTE: The Home page contains "My Activities" applet.

The same error occurs if we try to access any view in "Activities" screen.

By spooling the SQL we can see the cause of the error that the following SELECT statement:

- - -

SELECT

      ...

      T1.ACT_ALARM_FLG,

      T1.ACT_APPT_START_DT,

      T1.ACT_TODO_PLNSTRTDT,

      T1.ACT_TODO_PLNEND_DT,

      T1.ACT_APPT_REPT_FLG,

      T1.ACT_APPT_RPTEND_DT,

      T1.ACT_EVT_STAT_CD,

      T1.ACT_CAL_DISP_FLG,

      T1.ACT_TEMPLATE_FLG,

      T1.ACT_CAL_TYPE_CD,

      ...

   FROM

       SIEBEL.S_EVT_ACT T1

...

- - -

Indeed these columns do not exist in S_EVT_ACT table. They are

denormalized columns in S_ACT_EMP table. This table is the intersection

of link 'Action/Employee', the link used by the 'Employee' MVL.

Please note that a similar behavior is reproducible with other MVLs in

other BCs, e.g. 'Position' and 'Organization' MVLs in BC 'Account' and

'Contact' BCs. The same error will be encountered when accessing

"Accounts" or "Contacts" screen.

This behavior occurs because these MVLs are visibility MVLs. 'Employee'

MVL, for example, is involved in the visibility settings of 'Action' BC.

This one has indeed the following BusComp View Mode:

- - -

Name: Personal

Owner Type: Person

Visibility MVField: Owned By

Visibility MVLink: Employee

- - -

In fact setting Use Primary Join property to FALSE for visibility MVLs

is not supported. Visibility MVLs need to have a primary id defined and

primary join should be TRUE. The primary join has a special meaning for

visibility MVLs.

BUG 10474574 has been logged asking to document this

matter in Siebel Tools Reference and Object Types Reference guides.

Solution

The suggestion to achieve the customer's requirement is to create a new MVL based on the same link as the 'Employee' MVL and a MVF based on this MVL. This new MVL will have its 'Use Primary Join' set to FALSE and the new MVF will be used in the UI for the queries without the EXISTS operator.

References

BUG:10474574 - IT SHOULD BE DOCUMENTED THAT SET 'USE PRIMARY JOIN' TO FALSE FOR VISIBILITY MVLS IS NOT SUPPORTED

Applies to:

Symptoms

SBL-DBC-00105

Cause

Solution

As the date formatting depends on the session's NLS (National Language Support) settings, we suggested an adapted version that would work independent from the current NLS setting:

Applies to:

Symptoms

SBL-DBC-00105

Cause

Solution

As the date formatting depends on the session's NLS (National Language Support) settings, we suggested an adapted version that would work independent from the current NLS setting:

SBL-DBC-00104: Error retrieving next record from the database.

Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

Customer was running a batch job to deactivate workflows with following SQL:

SELECT
T1.CONFLICT_ID,
T1.LAST_UPD,
T1.CREATED,
T1.LAST_UPD_BY,
T1.CREATED_BY,
T1.MODIFICATION_NUM,
T1.ROW_ID,
T1.DESCRIPTION,
T1.NAME
FROM
SIEBEL.CX_INT_PARAM T1
WHERE
(T1.TYPE = 'PARAMETER') AND
(T1.PAR_ROW_ID = '1-2IKG')

This generates the following error in the EAIObjMgr log:

SBL-DBC-00104: Error retrieving next record from the database.
SQLParseAndExecute Execute 5 0 2009-05-12 17:34:09 ORA-24345: A Truncation or null fetch error occurred

ObjMgrSqlCursorLog Close 5 0 2009-05-12 17:34:09 Begin: Close Sql Cursor at 869b820
ObjMgrSqlCursorLog Trace 5 0 2009-05-12 17:34:09 SQL Cursor with ID 869B820 Fetch Rows: 20, Fetch All

Time: 0.003 seconds.
ObjMgrBusCompLog Error 1 0 2009-05-12 17:34:09 (buscomp.cpp (16578)) SBL-DBC-00104: Error retrieving next record from the database.

Running the SQL directly on the database returns 85 rows with no problems.

Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution

This schema change altered the DESCRIPTION column from VARCHAR(255) to VARCHAR(500)

This extra length on the column was causing an "buffer overflow" issue when an attempt was made to map the values to the logical siebel schema.

Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution

Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution

Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution

Applies to:

Siebel Tools - Version: 7.0.4.11 [14073] to 8.0.0.5 [20420] - Release: V7 to V8
Information in this document applies to any platform.

Symptoms

Customer increased the buffer size on the database and restarted the server it but we still experience the same problem.

Cause

This problem occured as a result of a physical db schema change.

Solution

SBL-DBC-00103: The DB2 database cannot be accessed.Maybe the server is down or the database that the server uses is incorrect or defective.

Applies to:

Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]
IBM AIX on POWER Systems (64-bit)

Product Release: V7 (Enterprise)

Version: 7.5.3 [16157] NLD Fin Svcs

Database: IBM DB2/UDB 7.2

Application Server OS: IBM AIX 5L 5.1

Database Server OS: IBM AIX 5L 5.1

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

Symptoms

Customer reported the following:

We experience thin client login problems on one of the servers. Siebel has been reinstalled as well as the eapps and the IHS server. An attempt to login still fails with the following error:

GenericLog      GenericLog      0       2004-05-24 18:03:53      ERROR   1800: [SWSE] Could not get an anon session...

GenericLog      GenericLog      0       2004-05-24 18:03:53      DEBUG   1800: [SWSE] Ending critical region   [ /fins_nld/anonSessionLock ] 0x30404978.

GenericLog      GenericLog      0       2004-05-24 18:03:53      ERROR   1800: [SWSE] Set Error Response (User: Session: Error: 00028356 Message: The DB2 database cannot be opened. Maybe the server is shutydownor the database has errors.Speak to your system administrator.(SBL-DBC-00103))

GenericLog      GenericLog      0       2004-05-24 18:03:53      ERROR   1800: [SWSE] [IBM][CLI Driver][DB2] SQL0102N The string constant beginning with "$(CurrentSQLID)" is too long. SQLSTATE=54002

Cause

DSCurrentSQLID set to $(CurrentSQLID)

Solution

For the benefit of other users:

The named subsystem ServerDataSrc had the parameter DSCurrentSQLID set to $(CurrentSQLID). Once this was changed to SSEROLE the problem was solved

SBL-DBC-00101: The user has cancelled the query.

Applies to:

Product Release: V7 (Enterprise)

Version: 7.5.3.15 [16279] Fin Svcs

Database: IBM DB2 for zOS and OS/390 v8

Application Server OS: Microsoft Windows 2000 Server SP 4

Database Server OS: IBM zOS

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

Symptoms

SBL-DBC-00101

Hi,

In last maintenance release of Siebel (7.5.3.15) there is a feature introduced

related to canceling query that is taking long time once submitted by the user. The Cancel Query

feature lets the user end a lengthy query and continue working in the same Siebel session, while

also terminating the query on the database and application server.

We made necessary CFG

change and are able to get a pop up to cancel the query. Once the cancel button is invoked, the

pop changes into canceling query (see attached document). However, we are monitoring from OM logs

and DB that none of the resources are being released and IO on the database is still clocking. We

are using DB2 v8 without connection pooling in this environment, however in production connection

pooling is enabled. The attached are logs from OM as well.

Thank you.

Solution

Message 1

For the benefit of other readers:

Customer was testing the cancel query feature on Siebel SIA version 7.5.3.15 connecting through IBM DB2 Connect Enterprise Edition version 8 FixPak 10 to IBM Db2 for z/OS v8.

The behavior was reported as follows:

a) Start a long running query.

b) The 'running/ cancel query' pop-up box is shown.

c) I can see the running thread in Db2 using DB2 PM.

d) I cancel the query selecting the 'cancel query' option, the pop-up box changes to cancelling query'.

e) The original thread still runs in Db2.

f) The 'SBL-DBC-00101' error never comes back until the query finishes by itself, in other words, if the query runs for 2 hours by itself, the error comes back in 2 hours.

The user is unable to do anything else in Siebel until the 'SBL-DBC-00101' error comes up.

After extensive investigation by both Siebel and IBM Support it could be determined that:

1) There is an issue using the cancel query feature with Siebel connection pooling pointing to IBM DB2 for z/OS v8 RDBMS servers. Change request #12-TNT0Z0 was opened for this topic some time ago and the fix needed in order to leverage this functionality has been introduced in Siebel Maintenance Release version 7.5.3.16.

(CONTINUED)

Message 2

(CONT.)

2) The behavior originally reported by the customer (without using Siebel connection pooling) could be identified as being due to the SQLCancel call taking place on a hostname/port that was not accepting requests. Therefore the SQLCancel was actually never issued on the RDBMS host.

IBM has a document discussing this type of occurrances:

http://www-1.ibm.com/support/docview.wss?rs=71&context=SSEPGG&uid=swg21210509

Once this was resolved the cancel query feature was working as expected.

Sunday, February 20, 2011

Tab Order in Grid Layout

Sequencing of fields in form applet can be of immense help for end user. It eases out the task of filling the form quickly and effectively. Siebel supports setting the tab order for the fields displayed in the form applet.

1 - Navigate to the Applet and select Edit Web Layout.

2 - In siebel tools toolbar select Format and Click on Set Tab Order or short cut key is Alt+O+O.