cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

After upgrading to 6.5, I got "ORA-01882: timezone region not found" error while connecting Performance Warehouse Database.

kbhagat
Contributor

After upgrading to 6.5 from 6.2 , I got "ORA-01882: timezone region not found" error while connecting to Performance Warehouse Database from Dynatrace Client. Refer attached screenshot.

Has anyone ever seen such issue and what did you do to fix it?

For me, I added the following property at
Dynatrace INI files so it loads at startup. Out of 2 environments that I upgraded, only one showed this issue.

-Doracle.jdbc.timezoneAsRegion=false

4 REPLIES 4

Joe_Hoffman
Dynatrace Leader
Dynatrace Leader

Instead of -Doracle.jdbc.timezoneAsRegion, try adding the following:

-Duser.timezone="+01:00
But put in an appropriate timezone offset value for your location.

kbhagat
Contributor

Thx. Joseph, yes I have seen this option as well to fix the issue. However, I am kind of surprised why it happened in one environment but not in another, as we have 2 identical setups as one lower and one say PROD environment.

Joe_Hoffman
Dynatrace Leader
Dynatrace Leader

Kishor, That is indeed an interesting mystery. I"ve never understood what changed to trigger the need for this parameter, but adding user.timezone does seem to fix it in all cases. Perhaps the OS has a default timezone set in one of your systems and not the other. I"m guessing.

kbhagat
Contributor

How is your solution different then what I used?