Hi, I noticed that OO has a very huge table OO_STEP_LOG_BINDINGS as follows and want to know what does this tables contain and if it is safe to truncate it ?
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more
Run the purge flow if you need to remove data from this tablespace - its used in conjunction with a few other tables. Removing data directly from this table without syncing across the rest of the relationship map will cause data lookup issues for reporting. 1M records really isnt that large for this table -- is there an issue occurring or just housekeeping?
Thanks a lot JarodMB for your reply.
I wanted to empty this table because it takes more than 80GB and in our dev plateform we do not have a large disk space (~~ 100 GB).
NB: For the number of records, the screenshot previously attached is from our dev server, the prod one has more than 80 M records.
Regards;
Hi Adel,
What JarodMB said is correct the best way to delete data from the database is via the purge procedures. Now in case of emergency in environments where data retention is not important (dev / test evnironments) truncating tables is faster and cheaper (from the I/O perspective).
The step log bindings table contains the input, output and transition data for all steps of executed flows. This data is only persisted after a step is completely executed. If data is removed from this table then you might have issues seeing step details in the OO Central UI drilldown. Judging from the usage in the screenshot this looks to be a 10.20 range OO install which is really old at this point. While procedures do exist for MSSQL and 10.20 range, i think it would be safe to truncate the bindings table for a quick fix.
Hope this helps,
Vlad