Applications Systems

ORA-01882 Timezone region not found error when you try to register an Oracle database

Users of DPA may get a timezone region not found error when trying to register an Oracle database.

First published date

10/10/2018 3:24 AM

Last published date

1/27/2022 7:03 AM

Overview

When trying to register an Oracle database, you may sometimes get an error similar to the following:

The timezone on the DB instance that you are trying to register is not compatible with the DPA timezone [Pacific/Tarawa].
Error Message: The timezone name/region on the client is not supported by the database. [error=java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-01882: timezone region not found ]

Product section

Database Performance Analyzer

Cause

There has been a change in the way JDBC handles timezone differences between the client and database. The old behavior was that the JDBC would compute a GMT offset and continue when there was a mismatch between the client timezone and the database timezone. However, the new behavior is to try to use the timezone name/region defined by the client. If the database does not support that particular name/region, we now get an error.

Resolution

We can ask the Oracle database we are trying to register to use the old JDBC behavior of computing a GMT offset. This will let us register the database instance.

  1. In the Register Instance Wizard, click Advanced Connection Properties. 
     
  2. In the Connection Properties field, enter oracle.jdbc.timezoneAsRegion=false, and then click OK.
  3. Continue registering the database instance.