Raising the limit to 2^64 won't help unless they also remove the feature that allows you to set the current SCN to an arbitrary multiple of 2^32, or scale up the number of SCN increments so that a "genuine" job can't possibly make them happen fast enough. My laptop can advance the SCN about 150,000 times per second - which means it will take slightly less than 8 hours to get through 4 billion - which means that's the longest time it will take for me to prepare my laptop to be a threat. Your only protection comes from knowing confident that your system can't increment the SCN faster than Oracle's limiting rate because I have to start by injecting a value that is "behind" a critical value and let you run on from there. Regards Jonathan Lewis http://jonathanlewis.wordpress.com Oracle Core (Apress 2011) http://www.apress.com/9781430239543 ----- Original Message ----- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx> To: <dedba@xxxxxxxxxx>; <oracle-l@xxxxxxxxxxxxx> Sent: Friday, January 20, 2012 3:46 PM Subject: RE: infoworld call They do indicate that this is in the plans at the bottom of MOS 1376995.1 -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of De DBA <snip> I would like to think that the hard limit in future versions will be put at a bit higher than a 48-bit integer... <snip> ________________________________ Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. -- //www.freelists.org/webpage/oracle-l ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1901 / Virus Database: 2109/4754 - Release Date: 01/19/12 -- //www.freelists.org/webpage/oracle-l