Oracle Data Guard monitored databases disappeared from Data Guard Tab.
DB_Oracle agent logs show these errors:
ERROR [ConnectionManagementThread-[OraclePool-hostname-INST]-[Thu Jun 23 03:33:35 UTC 2022][OracleProfile{host='hostname', instance='INST', username='sys', asSysDBA=true, ports='1571', useSSL=false, properties={oracle.jdbc.ReadTimeout=900000}}]] com.quest.qsi.fason.framework.connections.jdbc.JDBCConnectionImpl - Failed to create new connection. [OracleProfile{host='hostname', instance='INST', username='sys', asSysDBA=true, ports='1571', useSSL=false, properties={oracle.jdbc.ReadTimeout=900000}}]
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
The Linux server where the FglAM (Agent Manager) is running has the time zone set to Etc/UTC.
This time zone is the default for Azure Ubuntu VMs.
This error indicates that the time zone used for the JDBC connection to Oracle was not found by the Oracle server it's trying to connect to.
The FglAM logs show the timezone in the 001 log:
At the OS level, the timezone settings can be confirmed with these commands:
sudo ls -l /etc/localtime
lrwxrwxrwx 1 root root 27 Apr 4 21:40 /etc/localtime -> /usr/share/zoneinfo/Etc/UTC
timedatectl
Local time: Thu 2022-06-23 18:10:20 UTC
Universal time: Thu 2022-06-23 18:10:20 UTC
RTC time: Thu 2022-06-23 18:10:20
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no
The Oracle server doesn't recognize the Etc/UTC time zone in this example.
More information can be found in KB 97432.
The solution is explained in KB 97432.
For the example above, the solution would be switch the time zone to UTC.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center