Qlik Replicate: Failed to execute statement 'select distinct(tzname)...from V$TIMEZONE_NAMES'

Dana_Baldwin — Tue, 04 Jul 2023 14:04:17 GMT

When using Oracle source in a Qlik Replicate task, user gets this (or similar) error:

Failed to execute statement 'select distinct(tzname), to_timestamp_tz('2011-12-21 12:00:00.0 ' || tzname, 'YYYY-MM-DD HH24:MI:SS.FF9 TZR'), to_timestamp_tz('2011-06-21 12:00:00.0 ' || tzname, 'YYYY-MM-DD HH24:MI:SS.FF9 TZR') from V$TIMEZONE_NAMES' ORA-03113: end-of-file on communication channel

Resolution

In one example of this occurrence, the version of the Oracle client was newer than the version of the Oracle database in use on the source. Generally speaking, Oracle does not support older clients connecting to newer servers (but does support the opposite). This is because the older client is not "aware" of the newer features in the Oracle database.

The other thing to check is the time zone file on the client, it may not include all the entries available on the server: Choosing a Time Zone File | docs.oracle.com

The relevant note from the document linked above:

On the server, Oracle Database always uses a large [time zone] file. On the client, you can use either a large or a small file. If you use a large time zone file on the client, then you should continue to use it unless you are sure that no information will be missing if you switch to a smaller one. If you use a small file, you have to make sure that the client does not query data that is not present in the small time zone file. Otherwise, you get an error.

Environment

Oracle source

article Qlik Replicate: Failed to execute statement 'select distinct(tzname)...from V$TIMEZONE_NAMES' in Official Support Articles

Qlik Replicate: Failed to execute statement 'select distinct(tzname)...from V$TIMEZONE_NAMES'

Resolution

Environment