I just wanted to share another interesting topic with you.
My patient was complaining about the pains he had to perform saving in his Process Designer. He was not able to save his modifications (database vendor: db2).
I looked into the SystemOut.log and found the following:
Caused by: org.springframework.jdbc.UncategorizedSQLException:
PreparedStatementCallback; uncategorized SQLException for SQL [
END_SEQ_NUM = ?
BRANCH_ID = ?
AND END_SEQ_NUM = 999999999999
AND PO_TYPE = ?
AND PO_ID IN
(?,?)]; SQL state ; error code [-289]; DB2 SQL
Error: SQLCODE=-289, SQLSTATE=57011, SQLERRMC=USERSPACE1,
DRIVER=4.18.60; nested exception is com.ibm.db2.jcc.am.SqlException:
DB2 SQL Error: SQLCODE=-289, SQLSTATE=57011, SQLERRMC=USERSPACE1,
OK, so from the exception it seems like a DB-related problem. I discovered the SQLCode, the SQLState and SQLRMC. But what does it mean?
A quick research in the web showed us that SQLCODE=-289, SQLSTATE=57011 points to a problem where db2 is unable to allocate new pages in a table space. AHA! The save routine tries to update specific tables (in this case LSW_PO_VERSIONS), however since the database cannot allocate new pages in the table space, the exception is thrown and the saving is not possible.
I highly recommend to involve the DBA as another specialist in such cases. They should check the table space sizes.
However, I do remember some approaches from back in the days when I was a young DBA. So, the patient can add additional pages to the tablespace by running the following commands:
DB2 CONNECT TO database_name
DB2 LIST TABLESPACES SHOW DETAIL
DB2 "ALTER TABLESPACE tablespace_name EXTEND (ALL 100000)"
In this case, this treatment healed the patient and saving in Process Designer was possible again.
And if this does not help, take two of these and call me in the morning.
Your Doc D