Not sure about specific "oda functionalities", which is one of the reasons I
suggested you force Oracle to fix it, especially if they're supposed to be
providing you with "managed" (perhaps they forgot to put "mis" in front of
that) services.
I'd certainly shut down databases or anything else I cared about before I made
that change; and be prepared for "anomalies". On one of the servers, it will
suddenly be earlier than before and on the other, an hour will "never happen".
If you have application code that depends on non-localized date/times to track
things, you may see some of those "anomalies".
In a "perfect world", "systems" would account for this sort of thing; but, I
have yet to find said "perfect world". At least you're running NTP, so when
you get the timezones straightened out, you should be OK.
Good luck!
Clay Jackson
From: james Jose <josej8661@xxxxxxxxx>
Sent: Thursday, November 11, 2021 12:05 PM
To: Clay Jackson (cjackson) <Clay.Jackson@xxxxxxxxx>
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: ODA Time Zone
CAUTION: This email originated from outside of the organization. Do not follow
guidance, click links, or open attachments unless you recognize the sender and
know the content is safe.
also we can easily go and run below command on both nodes of oda without
breaking any other oda functionalities?
/usr/bin/timedatectl set-timezone America/Chicago
On Thu, Nov 11, 2021 at 1:52 PM james Jose
<josej8661@xxxxxxxxx<mailto:josej8661@xxxxxxxxx>> wrote:
Thanks Clay Jackson!!
ntpq command returns and peers retrurned list of servers as you can see below
% ntpq
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
ns1.xxx .INIT. 16 u - 1024 0 0.000 0.000 0.000
ftp8.xxx<ftp://ftp8.xxx> .INIT. 16 u - 1024 0 0.000 0.000
0.000
ntp14.xxx .INIT. 16 u - 1024 0 0.000 0.000 0.000
xx-xxx-xx-xx x.x.1x.x 4 u 36 1024 0 0.269 116.726 0.000
li1x7.memb .INIT. 16 u - 1024 0 0.000 0.000 0.000
ntpq>
On Thu, Nov 11, 2021 at 1:43 PM Clay Jackson (cjackson)
<Clay.Jackson@xxxxxxxxx<mailto:Clay.Jackson@xxxxxxxxx>> wrote:
I found this in MOS
Document 2250865.1
(oracle.com)<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.oracle.com%2Fepmos%2Ffaces%2FDocumentDisplay%3F_afrLoop%3D399713821423032%26parent%3DEXTERNAL_SEARCH%26sourceId%3DHOWTO%26id%3D2250865.1%26_afrWindowMode%3D0%26_adf.ctrl-state%3Dpa4txamhe_4&data=04%7C01%7CClay.Jackson%40quest.com%7Cc764d67395cc4a1ab9b308d9a54e9919%7C91c369b51c9e439c989c1867ec606603%7C0%7C0%7C637722579280944461%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=eXPB%2BflJBgY7xJEsN0XeCpfOp%2Fox8uio2zV7uc8zCAs%3D&reserved=0>
It uses timedatectl and looks pretty straightforward.
That said - if your agreement with Oracle calls for them to manage your ODAs,
(at least IMHO) this is a HUGE screw-up. It should be worthy of a Sev 1 SR
and if necessary Duty Manager Escalation; and you should make THEM fix it ASAP.
You should also make sure you're running NTP (Network Time Protocol) on both
nodes. A quick way to do that is to run "ntpq" from the Unix command line.
If it comes back, use the "peers" command, and if you see a list of servers,
you should be good. If it doesn't come back, or you don't see a list of
servers, that's ANOTHER issue.
Clay Jackson (Charter "Dinosaur")
From: oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>
<oracle-l-bounce@xxxxxxxxxxxxx<mailto:oracle-l-bounce@xxxxxxxxxxxxx>> On Behalf
Of james Jose
Sent: Thursday, November 11, 2021 11:31 AM
To: oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>
Subject: ODA Time Zone
CAUTION: This email originated from outside of the organization. Do not follow
guidance, click links, or open attachments unless you recognize the sender and
know the content is safe.
We have recently bought two node cluster ODAs and we are running oracle 12c and
the configuration of ODA is given below,
ODA X8 2 HA High Availability Configuration.
Oracle had set it up on the wrong time zone and one is on EST time zone and
another is on MT.
Seems like changing time zone on ODA is challenging one and oracle is not able
to help us yet. any tho
