Re: Re: Is it just me
- From: dbvision@xxxxxxxxxxxxxxx
- To: oracle-l@xxxxxxxxxxxxx
- Date: Fri, 13 Aug 2004 11:22:22 +1000
> Lisa Spory <lspory@xxxxxxxxx> wrote:
>
> Logminer won't help me track the WHO, especially since in this case the
> who is obscured through connection pooling and only available to the
> database via an explicitly set application context.
It could. Add a column to every table to keep the WHO. LAST_CHG_BY
is a good name. Then just update it for everyone, via trigger. It should now
end
up in the redo log. Of course you still would need to capture that from the
app server. App context would be the easiest, I guess. Avoid loosing deletes
by never deleting: use a flag column to say if the row is active or not.
> If I list partition by table_name, then how is the contention on my
> single table any different than having a separate table per table_name?
> (ignoring momentarily my desire to elegantly "slide" data off, which
> could be handled less elegantly to avoid contention issues instead).
Not very different. The idea with the partitioning would be precisely to
give you the low contention of the multiple log tables.
Not exactly linear, but near enough.
> I need to poke around and gather numbers related to the number of
> concurrent transactions I expect to support as well, since again, I am
> not auditing the whole database, mostly setup/parameter data.
Ah, that's MUCH better. Makes sense too.
Cheers
Nuno Souto
dbvison@xxxxxxxxxxxxxxx
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
