Siebel crash when using Multiple Tabs in Internet Explorer

Issue -

Siebel application crashes when the Siebel application is running in an IE7 or IE8 and a new tab is opened to the application.

If the user then navigates back to the original tab and uses any drilldown or selects a new tab the application will crash. The user may also note that labels of buttons and tabs become corrupt and appears as the names of fields from the applets


Supported documents -

This behavior is caused by the unsupported use of the multiple tab functionality available in the Internet Explorer 7 and Internet Explorer 8 browsers. This is discussed in the follow documents:

• Siebel Support for Internet Explorer 7 (IE7) (Doc ID 475275.1)
• Siebel Support for Internet Explorer 8 (IE8) (Doc ID 796015.1)

Solution -

If you Siebel version is 8.1.1.5, the apply the below QF to resolve the crash issue

•  8.1.1.6 Fix Pack (as part of Bug: 10592096)
•  Quick Fix QF0561 for the 8.1.1.5 Fix Pack (Patch Number: 13512346)

SBL-DEV-00462

SBL-DEV-00462 - DB zSeries error

This error is encountered when extending columns in Siebel tables, without providing the column name and column type.
1. Enter the name of the column (X_COLUMN_NAME) and the column type - Extension.

2. Enter the column length.

If the error message is still appearing, check the Tools -> View -> Options -> Database if the DB zSeries option is checked. If yes, then uncheck it and restart the tools.

Orphaned Transaction records

I recently was investigating an issue on growing S_DOCK_TXN_LOG table and came across the Oracle support Identified#477816.1. This issue was due to the Orphan records in S_DOCK_TXN_LOG

Details from Technote -

Siebel Systems introduced the concept of multi-operation transactions. For a multi-operation transaction there is one parent and many children. The child transactions have PAR_TXN_ID set to the parent transaction. In some cases, if the parent transaction is not present, Transaction Processor cannot delete the child transactions. These child transactions are then considered to be orphaned transactions.


To determine whether there are any orphaned transactions, run the following SQL query:

Oracle

SELECT B.TXN_ID, B.ROW_ID, B.PAR_TXN_ID, B.OPERATION, B.ITEM_NAME
FROM S_DOCK_TXN_LOG A, S_DOCK_TXN_LOG B
WHERE A.ROW_ID(+) = B.PAR_TXN_ID
AND A.ROW_ID IS NULL;

DB2 or MS SQL Server

SELECT B.TXN_ID, B.ROW_ID, B.PAR_TXN_ID, B.OPERATION, B.ITEM_NAME FROM S_DOCK_TXN_LOG A
RIGHT OUTER JOIN S_DOCK_TXN_LOG B ON B.PAR_TXN_ID = A.ROW_ID
WHERE A.ROW_ID IS NULL

The orphan records can be deleted using the Endtxnutl Utility or manually deleted.