I didn't have any problems with the DB job itself doing the cleanup. We did find that the messages are purged from the DB, but are retained in memory until the Text Conference Manager service is cycled. So clients will continue to see the messages past the purge date. CSCvk74438
~Chris -----Original Message----- From: cisco-voip [mailto:[email protected]] On Behalf Of Pawlowski, Adam Sent: Thursday, February 14, 2019 11:05 AM To: '[email protected]' <[email protected]> Subject: Re: [cisco-voip] Persistent Chat When we evaluated the cleanup jobs when 12.0 came out, it didn't actually work. It may now in a SU but 12.0 is sort of the stepchild and didn't get much attention so we're ignoring it. The best practices whitepaper explains the tables and sample jobs to clean it up, so we just added cleanup jobs to the needed tables in our Oracle db. It doesn't really get into the need to maintain indexes or things like that so we didn't do any such thing. Adam _______________________________________________ cisco-voip mailing list [email protected] https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwICAg&c=PzM68gSF_5r1R7BCE75oeA&r=Mtd_oRs0XS4YUZQRBEtJXoqyA13HyCrRFFUpCucX5ZI&m=5vgBadZyNdW8HsOPRyxtCRYamnjI_exhNcs4EInxfJY&s=jRJD4ICnZ9fioCYpYtt6Acss0ibeNHv9RJUMW2tufI8&e= _______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
