{"id":1019,"date":"2013-05-16T13:07:30","date_gmt":"2013-05-16T11:07:30","guid":{"rendered":"http:\/\/www.oradba.ch\/?p=1019"},"modified":"2013-06-04T16:06:36","modified_gmt":"2013-06-04T14:06:36","slug":"use-of-default_cleanup_interval","status":"publish","type":"post","link":"https:\/\/www.oradba.ch\/wordpress\/2013\/05\/use-of-default_cleanup_interval\/","title":{"rendered":"Use of DEFAULT_CLEANUP_INTERVAL"},"content":{"rendered":"<p>Following a question to the blog post&nbsp;<a href=\"https:\/\/www.oradba.ch\/wordpress\/2011\/05\/database-audit-and-audit-trail-purging\/\">Database Audit and Audit trail purging<\/a>, I noticed something interesting about the DEFAULT_CLEANUP_INTERVAL parameter. On one hand, it is mandatory to initialize the audit trail and to define a DEFAULT_CLEANUP_INTERVAL, on the other hand, the parameter is not used at all. Oracle explains this in the MOS note <em>Parameter DEFAULT_CLEANUP_INTERVAL of DBMS_AUDIT_MGMT.INIT_CLEANUP procedure <a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocumentDisplay?id=1243324.1\">[1243324.1]<\/a><\/em><\/p>\n<p>Quote Oracle Support (MOS Note <a href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocumentDisplay?id=1243324.1\">1243324.1<\/a>):<\/p>\n<blockquote><p>The dbms_audit_mgmt.init_cleanup parameter DEFAULT_CLEANUP_INTERVAL is not intended to be used to control the frequency of execution of audit management automatic cleanup. This parameter, although assigned a value during initialisation of audit infrastructure, is unused in current releases. However, in future releases it is intended to be used to control functionality which automatically partitions audit tables based on their archive frequency. This functionality already exists in the DBMS_AUDIT_MGMT package but is disabled in current releases. This is not a classified product bug, but expected behaviour.<\/p><\/blockquote>\n<p>According to the MOS Note <em>DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL Not Clearing FGA Audit Trail When Using Last Archive Timestamp <a title=\"[1532676.1]\" href=\"https:\/\/support.oracle.com\/epmos\/faces\/DocumentDisplay?id=1532676.1\">[1532676.1]<\/a><\/em> it could be a no go for audit purging if DEFAULT_CLEANUP_INTERVAL has not or never been. Conclusion initialize the audit trail and define a value for the default cleanup interval but manualy setup a purge job.<\/p>\n<p>I&#8217;m curious what Oracle plans for the future. Unified and self purging audit trail \ud83d\ude42<\/p>\n<h3>Reference<\/h3>\n<p>A few Metalink Notes related to Audit and Audit Management.<\/p>\n<ul>\n<li>Master Note For Oracle Database Auditing<em><\/em><\/li>\n<li>Known Issues When Using: DBMS_AUDIT_MGMT<em><\/em><\/li>\n<li>How to Truncate, Delete, or Purge Rows from the Audit Trail Table AUD$<em><\/em><\/li>\n<li>DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL Not Clearing FGA Audit Trail When Using Last Archive Timestamp<em><\/em><\/li>\n<li>Parameter DEFAULT_CLEANUP_INTERVAL of DBMS_AUDIT_MGMT.INIT_CLEANUP procedure<em><\/em><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Following a question to the blog post&nbsp;Database Audit and Audit trail purging, I noticed something interesting about the DEFAULT_CLEANUP_INTERVAL parameter. On one hand, it is mandatory to initialize the audit trail and to define a DEFAULT_CLEANUP_INTERVAL, on the other hand, the parameter is not used at all. Oracle explains this in the MOS note Parameter [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[8,13,64,5],"tags":[18],"class_list":["post-1019","post","type-post","status-publish","format-standard","hentry","category-11gr2","category-audit","category-audit-vault","category-oracle-database","tag-trivadiscontent"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p1aErb-gr","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":9867,"url":"https:\/\/www.oradba.ch\/wordpress\/2022\/03\/how-to-write-unified-audit-trail-records-to-syslog\/","url_meta":{"origin":1019,"position":0},"title":"How to write Unified Audit Trail Records to SYSLOG\u00a0","author":"Stefan","date":"23. March 2022","format":false,"excerpt":"With the introduction of Oracle Unified Audit, Oracle has completely redesigned the process of logging audit events. With the new unified audit trail, there is only one place where audit records are stored. Ok, the audit trail exists per PDB and for a read only database additionally somehow as a\u2026","rel":"","context":"In &quot;18c&quot;","block_context":{"text":"18c","link":"https:\/\/www.oradba.ch\/wordpress\/category\/oracle-database\/18c\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Oracle-SYSLOG-Audit-PDB.png?fit=1200%2C630&ssl=1&resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Oracle-SYSLOG-Audit-PDB.png?fit=1200%2C630&ssl=1&resize=350%2C200 1x, https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Oracle-SYSLOG-Audit-PDB.png?fit=1200%2C630&ssl=1&resize=525%2C300 1.5x, https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Oracle-SYSLOG-Audit-PDB.png?fit=1200%2C630&ssl=1&resize=700%2C400 2x, https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/Oracle-SYSLOG-Audit-PDB.png?fit=1200%2C630&ssl=1&resize=1050%2C600 3x"},"classes":[]},{"id":527,"url":"https:\/\/www.oradba.ch\/wordpress\/2011\/05\/database-audit-and-audit-trail-purging\/","url_meta":{"origin":1019,"position":1},"title":"Database Audit and Audit trail purging","author":"Stefan","date":"30. May 2011","format":false,"excerpt":"Setting up database audit is fairly easy. Since the availability of DBMS_AUDIT_MGMT the housekeeping of the audit trail is just a trifle. After the introduction of DBMS_AUDIT_MGMT in an post early this February, I would like to take a closer look at the housekeeping of the Audit Trail and provide\u2026","rel":"","context":"In &quot;10gR2&quot;","block_context":{"text":"10gR2","link":"https:\/\/www.oradba.ch\/wordpress\/category\/oracle-database\/10gr2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1396,"url":"https:\/\/www.oradba.ch\/wordpress\/2013\/08\/audit-vault-and-database-firewall-12-1-1-bundle-patch-1\/","url_meta":{"origin":1019,"position":2},"title":"Audit Vault and Database Firewall 12.1.1 Bundle Patch 1","author":"Stefan","date":"14. August 2013","format":false,"excerpt":"Oracle just released the new bundle patch for Audit Vault and Database Firewall 12.1.1. The patch can be downloaded on metaling as RPM patch set for existing installations or as full installation images for new installations. According the readme, the BP1 contains the July 2013 PSU 11.2.0.3.7 for the database\u2026","rel":"","context":"In &quot;Audit Vault and Database Firewall&quot;","block_context":{"text":"Audit Vault and Database Firewall","link":"https:\/\/www.oradba.ch\/wordpress\/category\/audit\/audit-vault-and-database-firewall\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1527,"url":"https:\/\/www.oradba.ch\/wordpress\/2013\/10\/avcli-audit-vault-command-line-interface\/","url_meta":{"origin":1019,"position":3},"title":"AVCLI Audit Vault command line interface","author":"Stefan","date":"18. October 2013","format":false,"excerpt":"When I started to deal with Oracle Audit Vault and Database Firewall (AVDF), I have always worked with the Web console. Since a few weeks I regularly use the AVCLI and start to like it. It is a simple java based command line utility, from which you can access Audit\u2026","rel":"","context":"In &quot;Audit Vault and Database Firewall&quot;","block_context":{"text":"Audit Vault and Database Firewall","link":"https:\/\/www.oradba.ch\/wordpress\/category\/audit\/audit-vault-and-database-firewall\/"},"img":{"alt_text":"AVCLI_Download","src":"https:\/\/i0.wp.com\/www.oradba.ch\/wordpress\/wp-content\/uploads\/AVCLI_Download-300x212.png?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":3240,"url":"https:\/\/www.oradba.ch\/wordpress\/2019\/09\/audit-trail-cleanup-in-oracle-multitenant-environments\/","url_meta":{"origin":1019,"position":4},"title":"Audit Trail cleanup in Oracle Multitenant environments","author":"Stefan","date":"20. September 2019","format":false,"excerpt":"A crucial aspect of any database audit concept is the management and maintenance of audit trails. Depending on the defined audit policies and the database activity, an audit trail can grow relatively quickly. Oracle Multitenant environments increase the operational effort because the root container and each PDB uses their own\u2026","rel":"","context":"In &quot;12R2&quot;","block_context":{"text":"12R2","link":"https:\/\/www.oradba.ch\/wordpress\/category\/oracle-database\/12r2\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1690,"url":"https:\/\/www.oradba.ch\/wordpress\/2014\/05\/audit-vault-and-database-firewall-12-1-2\/","url_meta":{"origin":1019,"position":5},"title":"Audit Vault and Database Firewall 12.1.2","author":"Stefan","date":"7. May 2014","format":false,"excerpt":"Oracle has just released a new Release of its Oracle Audit Vault and Database Firewall. The new release is immediately available on Oracle's Software Delivery Cloud. It look's like Oracle added a bunch of Enterprise-Grade Features like iSCSI SAN Disk, NFS Storage as well as SYSLOG integration. Starting with this\u2026","rel":"","context":"In &quot;Audit Vault and Database Firewall&quot;","block_context":{"text":"Audit Vault and Database Firewall","link":"https:\/\/www.oradba.ch\/wordpress\/category\/audit\/audit-vault-and-database-firewall\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts\/1019","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/comments?post=1019"}],"version-history":[{"count":5,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts\/1019\/revisions"}],"predecessor-version":[{"id":1163,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/posts\/1019\/revisions\/1163"}],"wp:attachment":[{"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/media?parent=1019"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/categories?post=1019"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.oradba.ch\/wordpress\/wp-json\/wp\/v2\/tags?post=1019"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}