ERROR|error creating messaging thread (48): err (12)

Holler - Increase the NumThreads in  swentobjsv.cfg along with required StackSize. The main problem with this error is of the threads starting up.  

Please remember that the Default Values for NumThreads / StackSize is calculated based of the system resources.  

NumThreads - 

If NumThreads is not set, then it is calculated with the formula - 

NumThreads = NumCPUs*DFLTMAXTHREADS*Multipler
Multipler = MAX (1, (2.4 - LOG (NumCPUs)))
where:
• NumCPUs is the number of processors on the system.

• DFLTMAXTHREADS is the default value, 5.

StackSize - 

This is set to login users thread stack limit. 

Reference :
https://docs.tibco.com/pub/iprocess-engine/11.1.0-september-2009/pdf/tib-iprocess-objects-server-administ rators-guide.pdf

Purge the Dead cases before Migration !

To avoid any migration (of cases) releated error , Please help to purge the dead cases and only migrate the live cases.


"swutil PROC RELEASE ... -m LIVE"

Happy Migration  :D No no Happy iProcess-ing !!

Error : (ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2')

UNDO Tablespace issue can take toll on Oracle database.

Simple reason for this problem is that UNDO Tablespace is running out of allocated disk space whilst attempting the procedure migration .That causes MIGRCASE instruction failure and the Oracle database would be required to rollback all of the changes it had made up until the UNDO failure.The MIGRCASE instruction would then be un-locked and another BG process would then be allowed to process that same MIGRCASE instruction which would start the migration process from the very beginning again.


1. How to find out the total cases which need to be migrated ?
Please run below query on iProcess database for a specific procedure .

select b.is_dead, b.major_vers, b.minor_vers, count(*)
  from proc_index a JOIN case_information b
    on a.proc_id = b.proc_id
 where a.proc_name = '<>'
 group by b.is_dead, b.major_vers, b.minor_vers
 order by b.is_dead, b.major_vers, b.minor_vers

To confirm on the migration error , you would also like to search "MIGRC" in the log files. You will find details in sw_warn.log file for case migration. Something similar to below :

CPLInstruction - Error> <-2>

Gather the Client Debug Logs

To validate the SSO to add users to Queues in iProcess, You can gather the client debug logs using below commands :

To see why that one procedure is listed twice, we would need to see Debug logs for an import/export.
Let's set environment debug.  

Steps:Log in as the the iProcess user.
Type this command at the Linux prompt:
DEBUG=ALL=255
export DEBUG

Then run the import and export commands, and validate  pstaffifc01.log file ffor errors, along with the plistP.txt file from this command

./plist -Pv > plistP.txt

Please make sure to stop the Debug, type this command, or log out and back in
unset DEBUG