RE: Large system level date changed
- From: "DIANNA GIBBS" <DIANNA.GIBBS@xxxxxxxxxxxxx>
- To: <Joel.Patterson@xxxxxxxxxxx>,<Smith.Steven@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 12 Feb 2007 12:43:39 -0600
I just ran down and ask our guys, but at a high level, we do not have a
full test
environment for Active Directory and we couldn't change the date/time
on production.
So when users tried to log in and authenticate to bring up the
environment,
AD thought they had timed out (future time/dates) and we couldn't get
past that
authentication part. We were able to test and start our Kronos
TEST environment that does not use AD with no issues. It's AIX 5.3
with Oracle 9206 RAC.
>>> <Joel.Patterson@xxxxxxxxxxx> 02/12/07 12:24 PM >>>
What were you active directory and/or web issues?
Joel Patterson
Database Administrator
joel.patterson@xxxxxxxxxxx
x72546
904 727-2546
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of DIANNA GIBBS
Sent: Monday, February 12, 2007 11:58 AM
To: Smith.Steven@xxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: Large system level date changed
We tried to simulate testing DST Friday in our Lawson environment.
AIX
5.2
and Oracle 9206. Server and database changed times back and forth
with no issues. We stopped/started Oracle with both times set and no
issues. We did have issues with the web server portion of the
environment and Active Directory.
>>> "Smith, Steven K - MSHA" <Smith.Steven@xxxxxxx> 02/12/07 9:56 AM
>>>
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
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
