We have a scenario in our teradata database where perm space is not getting released even when we delete all rows from the tables. Also, under the same condition the current perm of 2 replica tables with same rowcount, same structure and same index are deviating by 300% . when in a manual effort, we dropped and recreated the table, the currentperm was back to expected. Can somebody tell me any potential reason ?
Two possible reasons come to mind:
- It's a Temporal Table, all rows were closed
- ONLINE ARCHIVE was used, but not switched off. Check using dbc.ArchiveLoggingObjsV.
We have a scenario in our teradata database where perm space is not getting released even when we delete all rows from the tables. Also, under the same condition the current perm of 2 replica tables with same rowcount, same structure and same index are deviating by 300% . when in a manual effort, we dropped and recreated the table, the currentperm was back to expected. Can somebody tell me any potential reason ?