Re: New tool: ddldump

  • From: David Litchfield <david@xxxxxxxxxxxxxxxxxxxx>
  • To: Kurt Van Meerbeeck <kurtvm@xxxxxxxxxx>
  • Date: Wed, 30 Jun 2010 13:12:30 +0100

Hi Kurt,
It works on redo logs from Oracle 10 and 11. The redo log format is slightly different for earlier versions of Oracle and I'll need to poke around.

Hi David,

What versions of Oracle does it support ?


----- Originele e-mail -----
Van: "David Litchfield" <david@xxxxxxxxxxxxxxxxxxxx>
Aan: "Guillermo Alan Bort" <cicciuxdba@xxxxxxxxx>
Cc: oracle-l@xxxxxxxxxxxxx
Verzonden: Woensdag 30 juni 2010 00:40:36 GMT +01:00 Amsterdam / Berlijn / Bern / Rome / Stockholm / Wenen
Onderwerp: Re: New tool: ddldump

Hey all,
Thanks for the questions.
Yes - ddldump does work against archived redo logs.
Whilst ddldump is currently a windows console program it will work on redo logs from other OSes. That said, I'll write a version for Mac OS X and Linux shortly. There should be no impact on the DB at all. ddldump simply opens the file in read mode, parses it then outputs to the console. If you want to save the results to a file simply use the redirect >
C:\>ddldump redo01.log ddl > out.xml

On 29/06/2010 02:37, Guillermo Alan Bort wrote:

    Hey David,

       Nice tool, looks very interesting. Does it work on archived
    redolg files? I'll try it in my toy DBs this week... :-) I'd love
    to do it in productive ones, as it works on redo, I'm guessing it
    has no direct impact on the DB... is the source code available?


    On Mon, Jun 28, 2010 at 9:50 PM, David Litchfield
    <david@xxxxxxxxxxxxxxxxxxxx <mailto:david@xxxxxxxxxxxxxxxxxxxx>>

        Hey all,
        As part of a larger project, I've written a small tool called
        ddldump that parses Oracle redolog files and dumps any DDL
        statements in an XML format. ddldump has been developed with
        forensic investigations in mind but can of course be simply
        used by DBAs to peruse the DDL in their logs. You can download
        it from
        David Litchfield
        v3rity Ltd

        C:\app\david\oradata\orcl11g>ddldump REDO01.log ddl

        <?xml version="1.0"?>
        <ltimestamp>01/02/2010 15:26:02</ltimestamp>
        <TIMESTAMP>04/03/2010 01:16:34</TIMESTAMP>
        <SQL_STATETMENT>create user hax0r identified by VALUES
        '9A3502887F7210C4' </SQL_STATETMENT>

        RDRCOFST is the hexadecimal offset into the redolog file where
        the redo entry containing the DDL statement can be found
        CHVCOFST is the hexadecimal offset into the redolog file where
        the change vector containing the DDL statement can be found
        TIMESTAMP is the time and date when the redo entry was written
        to the log file.
        SESSION_USER is the user that is logged on and initiated the
        DDL statement
        CURRENT_USER is the user under whose authority the DDL
        actually executes. If session_user and current_user are
        different it could be indicitive of a SQL injection attack.
        SQL_STATEMENT is the DDL that was executed.
        SCHEMA, if present, is the schema upon which the DDL acts.
        OBJECT, if present, is the object upon which the DDL acts.

Other related posts: