MySQL provides the mysqlbinlog utility to parse binary transaction logs for any number of purposes which may include replication, auditing, or troubleshooting. Oracle also provides this functionality through a PL\/SQL package called dbms_logmnr, more commonly referred to as “Log Miner”.<\/p>\n
MySQL is very convenient in that all you need to enter at the command line is…<\/p>\n
mysqlbinlog log_file_name<\/p>\n
With Oracle, you must do some more “work”, but it is arguably more flexible since it is an API that you can call from any number of front end applications. See the article on using python for an example.<\/a> It can also be run from a remote server to aid in flexibility.<\/p>\n Each has its own merits, and each are immensely useful.<\/p>\n","protected":false},"excerpt":{"rendered":" MySQL provides the mysqlbinlog utility to parse binary transaction logs for any number of purposes which may include replication, auditing, or troubleshooting. Oracle also provides this functionality through a PL\/SQL package called dbms_logmnr, more commonly referred to as “Log Miner”.…<\/p>\n\r\nbegin\r\n dbms_logmnr.add_logfile(logfilename => '&log_file_name');\r\n dbms_logmnr.start_logmnr(options => dbms_logmnr.dict_from_online_catalog + dbms_logmnr.no_rowid_in_stmt);\r\n for cur in (select *\r\n from v$logmnr_contents) loop\r\n --do something with data\r\n end loop;\r\nend;\r\n\/\r\n<\/pre>\n