Are there tips for writing Oracle DDL Triggers for auditing? Or should I just use AUDIT? I've been tinkering with writing a trigger to log my table creation and manipulation for later tracking and review.

The challenge is that my trigger logic is stored in the same schema on which I've put the trigger.  Because of this, whenever I recompile the trigger or the package or whatever, the trigger itself fires. Also, if another component requires a recompile, the trigger fires.

The trigger has been failing and, in fact, locking my database session.  I have started putting guards on the trigger to prevent this and haven't worked it out yet.

Perhaps someone on the site has experience or advice?  Or just tell me to use AUDIT commands instead?
Why do you want to log DDL on your DB? just for auditing?
a trigger is highly not recommended because that if you have an error you can't even disable the trigger.
consider this scenario:


Trigger fails and cashes all DDL operation on the table
You try to disable the trigger
The trigger is invoked (back to step 1)


I suggest you'll take a look at Oracle DB vault and audit vault
http://docs.oracle.com/cd/E14472_01/doc.102/e14459/toc.htm

It got some really nice features for monitoring and controlling administration commands