Dumb Developer tricks

From: Goulet, Richard <Richard.Goulet_at_parexel.com>
Date: Mon, 18 Jan 2010 13:51:23 -0500
Message-ID: <6B0D50B70F12BD41B5A67F14F5AA887F0392DA2C_at_us-bos-mx022.na.pxl.int>


        I'm going to start a new thread away from the Undo tablespace link because, well this is just dumb & I'm wondering how many others have heard similar things. BTW I've changed names to protect the guilty.

Hello all,

  we had a meeting with Xxxx today about commit and rollback operation.   Xxxx advices us to not use the default Oracle commit/rollback, but to use instead these two procedures :

 Goals of this procedure is to store in TRANSACTION_LOG table records about transaction performed.
 These records will be used when synchronisation will be performed between XXX online and XXX offline. It enables mechanism used to manage the synchronisation to prevent lost of data on long running synchronisation.

 So, now, each time a script that modified data must be executed, we must too use these two procedures to commit or rollback.

 Feel free to forward to other people that deals with transaction somewhere in development/database administration/...

Dick Goulet
Senior Oracle DBA/NA Team Lead
PAREXEL International
900 Chelmsford St, Suite 310
Lowell, MA 01821

The information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer.

Received on Mon Jan 18 2010 - 12:51:23 CST

Original text of this message