The IFSAPP_DATA tablespace filled up because of an oversized TRANSACTION_SYS_LOCAL_TAB (the background-jobs table), and after reducing the number of jobs via system parameters, the table's row count in the client dropped back down — but the tablespace itself hasn't shrunk, and the table's actual row count at the database level is still far higher than what's shown in IFS.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Run ALTER TABLE TRANSACTION_SYS_LOCAL_TAB SHRINK to lower the table's high-water mark and release the freed space back to the tablespace — note this reclaims space within the tablespace but won't shrink the underlying Oracle datafile itself. Separately, make sure the scheduled 'Rebuild Index' job is actually running on a regular basis; indexes aren't automatically kept compact after large volumes of rows are deleted unless that job is scheduled and executing, so a stale index-rebuild schedule can leave both space and performance issues even after the row count itself is brought back under control.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions