Selecting the Procedures section within the iProcess Workspace (Browser) does not list all the expected procedures.

Reviewing the swentobjsv01.log files it can be seen an error is being reported,

80118|82C8E700|06/12/2019 02:43:13.142|00005000|ERROR|dbs_name_to_dbs failed for field(FLDNAME) in procedure(PROCNAME), err(-2); procedure can not be cached
80118|82C8E700|06/12/2019 02:43:13.142|00000001|ERROR|error getting field definitions
80118|82C8E700|06/12/2019 02:43:13.142|00000001|ERROR|error in fill_proc_def, rc=-145 proc=PROCNAME node=ipenode
80118|82C8E700|06/12/2019 02:43:13.142|00000001|ERROR|process_transaction() failed, rc=-136 Message Code(PE)

The error indicates a problem with iProcess Tables. Using the plist utility results in:

plist -s
There are no databases on node ipenode

plist -t
There are no databases on node ipenode

The cause of the problem is the relevant iProcess Tables are not installed correctly. This means the SPO process cannot cache the procedure definition(s) for the procedures have fields linked to iProcess Tables.

All supported platforms and databases

Reviewing the iProcess Engine database tables it was found the table information existed in the tsys_dbs_ tables but not in the dbs_ tables. However, the Table Area for updates made to indicate a Move System Information (MOVESYSINFO) is required was not ticked.

A dummy edit was made to each iProcess Table which resulted in the Table Area flag being updated. A MOVESYSINFO was performed and the table data was successfully copied to the dbs_ tables.

As a result, all procedures were cached correctly after the SPO process was restarted and all procedures were listed and visible in the iProcess Workspace (Browser).

Procedures not listed or visible in the iProcess Workspace (Browser)

Refer to the relevant TIBCO iProcess Engine (database variant) Administrator’s Guide for details of the iProcess Tables.