Re: Would this be a bottleneck?

In general it is easier for Oracle to deal with things that lie within its range of activity, i. e. an RDBMS. So, yes, your idea is good. Inserts do not impose that much of an overhead to redolog and rollback segments like updates and deletes do. Further, you can access your RDBMS logs from any client whereas you have to think of transferring your file system logs to the examining client.

The only thing you have to take care of is the transaction protection of log entries.

Example: you want to log any changes to a table. Some procedure starts such a change, inserts the log entry within the same transaction but then it rolls back. This means that also the log entry is rolled back. If you want to keep the log entry in your log table you have to insert it within an autonomous transaction.

Martin

Buffy The Cache Coder wrote:
>
> I need to know if the following is a good idea.
> Or would it be a performance bottleneck.
>
> I have upto 100 programs running at once
> that make logs. And, I need an 'overseer'
> program that tracks the logs. And possibly
> gives updates to an enduser based on
> log entries.
>
> Instead of having 100 files to track, I could
> have all 100 programs insert log entries into
> a log table on Oracle. This would make it
> much easier for an 'overseer' program to
> track what is going on.
>
> The question is, would this be a serious
> performance bottleneck. Keep in mind
> the log table is used just for inserting,
> rarely any updating, and periodical reading.
>
> comment? thoughts? suggestions?
>
> thanks in advance.
Received on Thu Mar 07 2002 - 02:21:22 CST