🚀 go-pugleaf

>I am willing to wager that most tools are using the
>Connection classes getMetaData() from the java.sql
>package, which probably uses only default settings and does
>not allow overrides to these methods or accessor methods
>(sets) for database vendor specifics (such as those in
>Oracle). However, the Oracle drivers may allow for this
>directly. Since I am not at work, and I do not have Oracle
> at home, I cannot test my theory. I will do so this week
>(when I get some time) and let you know what I find,
>if you do not beat me to it :)

Paul, 

You were on the right track. I am no Java expert but I 
managed a small program that connects with the database and
gathers metadata. I discovered that databaseMetaData.getIndexInfo 
causes the Analyze. Even if Connection.getMetaData()is 
typecast with OracleDatabaseMetaData. 

// code snip - causes analyze but should not 
rset = metadata.getIndexInfo(null, "SCOTT","EMP",false,true);

With that info I googled 'DatabaseMetaData.getIndexInfo analyze'

I found this on OTN: 
http://forums.oracle.com/forums/thread.jspa?threadID=210782

I looked up the bug number mentioned on MetaLink. It describes the issue exactly but the bug has no resolution and has been dormant since 07-FEB-2003. 

Good call.