DBAs noticed that since the upgrade to version 21, the database RT table is growing at an exponential rate. Automic maintenance executes daily (Archive, Reorg and Remove/Unload).
Why is the RT table not staying at a manageable size? DBAs are having to increase the filesystem to compensate but that is only a band-aid solution.
The DBAs just reported to me that the filesystem has grown by 5 gb in the past 2 days.
Release : 21.0
Take a look at your older ini files for the reorg an unload (ucybdbre.ini and ucybdbun.ini respectively). Do they include no_archive_check=1?
Some question to ask:
Do you have a requirement to records in a flat file (archive) for auditing?
Or is okay to simply delete the records from the database?
If it's okay to delete them, then updating the no_archive_check to 1 in both ini files will allow for deletion without archiving.
It may be that after the upgrade, since new ini files are being used, no_archive_check is set to 0 which means that the reorg will not flag rows for deletion and the unload will not delete them unless the archive is run first.