Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Database Performance Analyzer (DPA) > ORA-01882 Timezone region not found error when you try to register an Oracle database

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

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 2,302 Votes: 0 Revisions: 9

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 ]

Environment

All versions of DPA

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
    dpa-9.1-register-instance-wizard-oracle-rds.png 
  2. In the Connection Properties field, enter oracle.jdbc.timezoneAsRegion=false, and then click OK.
  3. Continue registering the database instance.

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.

Last modified
19:16, 22 Jun 2016

Tags

Classifications

Public