Last Modified: Sep 23, 2022
See more info
Known Affected Versions:
11.6.1, 11.6.0, 11.5.4, 11.5.3, 11.5.2, 11.5.1, 11.5.0, 11.4.1, 11.4.0, 11.3.0, 11.2.1, 11.2.0, 11.1.0, 11.0.0, 10.2.4
12.1.0, 11.5.4, 11.4.1 HF10, 10.2.4 HF13
Opened: Oct 14, 2015
Related Article: K73453525
Occasionally, the OJDBC driver reads a time zone file that it cannot understand, which causes Oracle monitors to fail.
Cannot use direct Oracle monitoring to ensure the backend is functionally operational. OJDBC driver seems to negotiate the time zone for the session, and instead of 'UTC', it attempts to change the time zone to: 'Universal', 'Zulu', 'Etc/Universal', 'Etc/Zulu', which will cause the monitor to fail, and not execute the actual monitoring. Note: Other time zones might be affected.For example, a similar issue might happen with the time zone set to GMT, which can become 'Greenwich' because of the same functionality.
- The system uses ojdbc6.jar for Oracle monitor functionality. - The UTC time zone is configured. - Contents of the /usr/share/zoneinfo directory are arranged so that the 'UTC' file is not the first in the list. (Versions prior to 10.2.4 use the 1.4-compatible ojdbc14.jar driver. The objdbc6.jar OJDBC driver, as supplied by Oracle for Java 6 (aka 1.6) auto-detects the local system's time zone name by scanning and comparing files under /usr/share/zoneinfo. The filenames are created during installation, and seem to depend on the 'Directory Hash Seed' of the /usr filesystem, so there is no predictable result.)
Although there is no reliable workaround, reinstalling might resolve the issue, as may using another time zone.
Oracle monitor functions now as expected with UTC and other time zones.