Re: Timezone setting on Exadata - daylight savings time

From: De DBA <dedba_at_tpg.com.au>
Date: Sun, 1 Oct 2017 18:18:49 +1000
Message-ID: <aa988dde-75b3-0ea3-8ee4-0e2b9d6ee456_at_tpg.com.au>



Update:

After shuttling the SR between RDBMS and NLS groups, Oracle allowed us to change the time zone settings on just the compute nodes. They were not very clear on whether a reboot was necessary and advised us that ".../for os level changing timezone you might need to reboot server to effect the value/. /please/ _/check with Unix admins/_/once on that/... " That was the NLS group, who were apparently oblivious to the fact that the SR was raised as a Hardware/OS SR. By the UNIX admin... :/

Oracle Support is not what it used to be...

So we rebooted both nodes. All good & dandy, except the database still did swap to DST after all that. Turns out that the bash profiles for both the oracle and grid home owners had the TZ variable set to the original value, but removing that still made no difference.

Checking the environment of the running clusterware processes, all of them including the databases started with the clusterware tool srvctl, have yet another setting for TZ. This is now the situation:

Where does the ocw get it's timezone setting from? The TZ it uses is not expected or documented..

Cheers,
Tony

On 29/09/17 20:45, De DBA wrote:
>
> Hi Franky,
>
>
> Thanks, I did find that doc but it doesn't go into detail - especially whether it is OK to have one or two components run with another timezone than the rest of the stack. Also, I cannot find whether I need to reboot Linux after changing the /etc/localtime file to make the OS notice the change..
>
>
> Cheers,
>
> Tony
>
>
> On 29/09/17 19:41, Franky Weber Faust wrote:
>> Hi Tony,
>>
>> You can follow this doc 1931729.1
>> Since Exadata runs Linux it should work for you.
>>
>> Regards,
>>
>> Franky
>>
>> On Fri, 29 Sep 2017 at 00:55 De DBA <dedba_at_tpg.com.au <mailto:dedba_at_tpg.com.au>> wrote:
>>
>> G'day.
>>
>>
>> A BI collegue just realised that this weekend part of Eastern Australia will change over to Daylight Savings time. Our exadata is in that part, and set up with the local timezone, but the business itself is not. As a result the database will likely change to AEDT with the rest of the datacentre, throwing all kind of schedules in disarray as batch jobs running in Queensland will continue to run at their normal time (relative to UTC).
>>
>>
>> I can't seem to find any information on how to disable daylight savings time safely for the entire exadata. Any ideas?
>>
>>
>> Cheers,
>>
>> Tony
>>
>> --
>>
http://www.freelists.org/webpage/oracle-l
>>
>>
>> --
>> /Kind regards / Cordialmente / Saludos cordiales / Sincères amitiés / Mit freundlichen Grüßen / Cordiali saluti,/
>>
>> Franky Weber Faust
>> Oracle DBA
>> Skype: franky.faust
>

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Oct 01 2017 - 10:18:49 CEST

Original text of this message