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.

Tutorials - Service Oriented Architecture

Every week, I will be providing links to the tutorials which I feel would be a good introduction to the SOA world.

Title - Service Oriented Architecture

Description -

This article gives a good overview of what SOA is all about.

• SOA Definitions
• Why SOA

• SOA Principles

• Service Orientated Design and Development

• SOA and Web Service Protocols

• SOA, Web 2.0 and mashups

• SOA 2.0 or Advanced SOA

• What are the Challenges faced in SOA Adoption

• Criticisms of SOA

• SOA and Business Architecture

• Jargon

• Literature

• References 
 
Link:
 
http://en.wikipedia.org/wiki/Service-oriented_architecture
 
This tutorials sections is not just going to be based on wiki's, but will be based out many important tutorial sites, my documents, and others.
 
Happy Learning !!!

Do you know about SWE Log ?

SWE Log

Some of the issues like Symbolic URL or issues related to the portals, SWSE, Web server issues cannot be debugged using the regular log files. For this reason, Siebel provides the ability to enable SWE Log.

To enable the SWE log file

1. Open your application’s configuration file, for example uagent.cfg.

    Configuration files are located in the siebsrvr_root\BIN\language_code.

2. Under the [SWE] heading in the .cfg file, add the following parameter:

    [SWE]
    EnableSWELog = TRUE
 
3. To change the log directory include the parameter  - 'LogDirectory' in the [SWE] section
 
4. Restart the object manager to allow this new parameter to take effect.