Re: infoworld call
- From: Andy Klock <andy@xxxxxxxxxxxxxxx>
- To: stellr@xxxxxxxxxx
- Date: Tue, 24 Jan 2012 15:29:28 -0500
When I looked at this last week (and again after readings Riyaj's excellent
blog regarding the soft limit) I was able to bump my SCN to 12 trillion
(the number of seconds since 1/1/2088 * 16384) . After which my SCN growth
was throttled at 16K per second. Fine, I feel safe. But then I thought to
myself what happens if I fast forward my system date so far in the future I
no longer have a limit and then increase my SCN accordingly?
SQL> select to_date('01/01/1988', 'MM/DD/YYYY') +
((281474976710656/16384)/24/60/60) newscn from dual;
NEWSCN
--------------------
2532-MAY-29 01:53:04 <-- theoretical date in which I can advance my SCN to
the max
SQL>
[root@bbh ~]# date -s "29 MAY 2532 01:53:04"
Thu May 29 01:53:04 EST 2532
SQL> select sysdate from dual;
SYSDATE
--------------------
1988-JAN-01 00:01:32
SQL> !date
Thu May 29 01:54:56 EST 2532
1988 again. Deja vu. My date wrapped. I lowered my time a bit:
[root@oimtest ~]# date -s "29 MAY 2400 01:53:04"
Mon May 29 01:53:04 EST 2400
SQL> select sysdate from dual;
SYSDATE
--------------------
1992-FEB-07 06:28:53
Definitely wrapping, but then I remembered there was an "end date" to
Oracle. Found my way to :
*OERR: ORA 1513 invalid current time returned by operating system [ID
18913.1]*
Which implies that I should get an error if the OS date is not between 1988
and 2121. I did not get an error but my database SCNs seem to be safe for
now....
Andy
On Tue, Jan 24, 2012 at 10:57 AM, Ray Stell <stellr@xxxxxxxxxx> wrote:
> On Tue, Jan 17, 2012 at 10:33:14AM -0500, Ray Stell wrote:
> >
> http://ifwnewsletters.newsletters.infoworld.com/t/7944027/121304526/606338/0/
>
> followup article:
>
> http://www.infoworld.com/d/security/the-oracle-flaw-clarifications-and-more-information-184775?page=0,0&source=IFWNLE_nlt_wrapup_2012-01-23
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
