RE: Large system level date changed

Hmmm...learn something new every day...I've never heard of this issue before....  

I did a quick MetaLink search, but none of the documents I ran across seem to give a clue as to what a "sufficiently large" time gap is.....  

-Mark  

--

Mark J. Bobak

Senior Oracle Architect

ProQuest Information & Learning

There is nothing so useless as doing efficiently that which shouldn't be done at all. -Peter F. Drucker, 1909-2005  

From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Smith, Steven K - MSHA
Sent: Monday, February 12, 2007 10:56 AM To: oracle-l_at_freelists.org
Subject: Large system level date changed

Testing for the DST time changes is being planned here. It's actually going to have a minimal impact, but the testing needs to happen. Anyway, the request is to change the server level dates to the second Sunday in March to simulate the DST change.  

I understand that Oracle should/doesn't use the system dates to keep transaction continuity. I was about to give my input that changing the system date should not have an issue on the database itself until I ran into metalink note # 253977.1  

That note says:  

"While opening the database, Oracle compares the given SCN value with the reasonable upper limit value calculated based on the system date. If Oracle detects the provided scn is too large, ORA-600[2252] would be raised."  

Now I'm a little concerned that when we change the system date back to the current correct date, I might have issues.  

Anyone have any experience with this?  

Steve Smith

Envision Technology Partners / MSHA MSIS Team

Desk: 303-231-5499    

--

http://www.freelists.org/webpage/oracle-l Received on Mon Feb 12 2007 - 11:13:26 CST