Re: Multiple independent transaction handle by a stored procedure

You can't really have concurrent tranactions on the same connection. One trick that you could play is to use oracle pipe to communicate to another process. For example, you could have one stored procedure which would receive messages. It would log any error messages until it is sent some sort of termination message. Your other procedure would just send messages through the pipe and not need to commit them. When you process is complete, you can send another message to the other process that will cause it to terminate.

Next, you have to run both of them... Youcould submit both of them to the job queue for a one time execution. Just make sure that you have enough job queue process free to run both of them.

"Bjørn Dybdal" wrote:
>
> Does anybody know a way to handle multiple independent transactions inside a
> stored procedure.
>
> My problem is that I have to do some update in my database. If I encounter
> problems during my processing
> I want log these problems in a seperate table XX.
> If my updating process ends out with a rollback I don't want my logging into
> table XX to be rolled back.
>
> Med venlig hilsen
> Bjørn Dybdal
> Datani A/S
> Hørkær 12A
> 2730 Herlev
> Tlf: 44 53 41 44
> mailto:bd_at_datani.dk
Received on Tue Nov 03 1998 - 10:35:20 CST