Re: Unique index access path seems very slow

>>> this test which we are doing for ~1hr worth of date range, is to
consider in case we have some backlog to catch up during system down time etc.

Just as an indication of thinking carefully about what you need to test:

Your latest run for one hour's worth of data was about catching up in the event of a backlog, and that completed in 11 minutes, which means you've won back 49 minutes, and now have to start the next run immediately to catch up 11 minutes of data, if if that takes less than 5 minutes your next run (you said every 5 minutes) is back on schedule. So why are you thinking you need a 2 or 3 minute completion time for 1 hours worth of data?

Realistically what's the worst case backlog you want to deal, and how fast do you want it cleared?
Say you have an 8 hour backlog and you can clear one hour of data in 15 minutes, what does that do for you? Winning back 45 minutes every 15 minutes means that after 8 runs you're down to a 2 hour backlog; after another 2 runs you're down to 30 minutes backlog, and after one more run you're on schedule. So you've caught up an 8 hour backlog in less than 3 hours.

--
http://www.freelists.org/webpage/oracle-l