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.






תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - 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: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא