Anyone using Optim Data Growth to delete data from a DB has invariably run into the issue of having a Parent table in an Access Definition and being relegated to single key deletes against it. Yep, even if you set a delete strategy to use multiple keys, Optim will issue a sever warning code and then override your delete strategy to use one key at a time.
I am not sure why it does this because DBMS engines do allow for multiple keys in a Delete statements against parent tables. Plus, Optim always deletes child tables first, so there is really no chance of orphaning a child row between the DBMS verifying this and Optim already cleaning up child data first.
I opened a PMR to look into this and was told it had to go the RFE route. I submitted the RFE, but I'm guessing without some upvotes, this will not get attention. If you would like to see this single-key delete restriction on parent tables looked at and (hopefully) removed, please follow the link below to review my RFE and vote for this enhancement.
https://ibmanalytics.ideas.aha.io/ideas/OPTIM-I-119I think this is an easy win for all involved and would greatly improve the delete performance of the tool. Thanks for reviewing this!
------------------------------
Keith Tidball
Progressive Insurance
------------------------------
#InfoSphereOptim#Optim