Skip to main content

Siebel Workflow Instance Monitor not working

Issue Details:

In "Active Workflow Processes" Monitoring Level of  workflow is set to "3 - Detail" but when check the "Workflow Instance Monitor" there are no "Step Instances".

Step to find the root cause:

  1. Set the Workflow Monitoring Level to "3 - Detail".
  2. Increase the Application Object Manager (in this case Public Sector) logs to level 5.
  3. Re login the application and invoke the workflow. 
  4. Find the Public Sector OM logs. (Path: C:\Siebel\15.0.0.0.0\ses\siebsrvr\log)
  5. Open the log file (PSCcObjMgr_enu_*.log) and search "Instantiating".
  6. When you find your Workflow step name (set in workflow) scroll down and find the place where Siebel is inserting the "Step Instance" and "Process Properties".
  7. Carefully read the end lines and you will find the issue.
  8. In my case below was the issue mentioned in logs:

SQLParseAndExecute    Execute    5    000000fa635f2ee4:0    2022-10-31 21:10:15    OCIStmtExecute: DML error or affected 0 rows
ObjMgrBusCompLog    Error    1    000000fa635f2ee4:0    2022-10-31 21:10:15    (oracon.cpp (3896)) SBL-DBC-00111: An error has occurred writing to a record.
Please continue or ask your systems administrator to check your application configuration if the problem persists.
SQLParseAndExecute    Execute    5    000000fa635f2ee4:0    2022-10-31 21:10:15    ORA-01653: unable to extend table SIEBEL.S_WFA_INSTP_LOG by 8192 in tablespace SIEBEL_DB

Solution:

As from the logs it is clear that this issue is due to the table space. For fix care fully TRUNCATE the table. Use below two TRUNCATE statements, possibly when you remove the data from  "Step Instance" will also cascade delete the "Process Properties".

Solution Implementation:

Open Oracle SQL Developer client, connect the db and use below queries.

Step Instance:

SELECT COUNT(*) FROM S_WFA_INSTP_LOG
SELECT * FROM S_WFA_INSTP_LOG

--TRUNCATE TABLE  S_WFA_INSTP_LOG

Process Properties: 

SELECT COUNT(*) FROM S_WFA_STPRP_LOG
SELECT * FROM S_WFA_STPRP_LOG

--TRUNCATE TABLE  S_WFA_STPRP_LOG

Similar Post:

How to delete Siebel Workflow Instance monitor logs SQL Developer

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...