ORA-01882: timezone region not found in Weblogic

While trying to create a connection pool to oracle db , following error occurs in weblogic app server.

ORA-00604: error occurred at recursive SQL level 1 ORA-01882: timezone region not found
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:382)
oracle.jdbc.driver.T4CTTIfun.processError(T4CTTIfun.java:573)
oracle.jdbc.driver.T4CTTIoauthenticate.processError(T4CTTIoauthenticate.java:431)
oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:366)
oracle.jdbc.driver.T4CTTIoauthenticate.doOAUTH(T4CTTIoauthenticate.java:752)
oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:366)
oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:538)
oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:228)
oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:280)
oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:482)
oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:156)
oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:101)
com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:745)
com.bea.console.actions.jdbc.datasources.createjdbcdatasource.CreateJDBCDataSource.testConnectionConfiguration(CreateJDBCDataSource.java:458)

The above time zone error usually comes as weblogic queries DB for timezone status.
The above error will show up when there is timezone difference between the database machine and the weblogic application server JVM.

To solve this error please follow below steps:

It seems that each server(DB and weblogic) has a different timezone at OS level.

To resolve the timezone issue we need that both DB and in the JVM should have same timezone set.

We have two ways of doing it:

1. Set same timezone in both the DB and weblogic machine at OS label.(Ask your administrator to do so)

2. If OS label is not allowed you can go for the below JVM label, i.e by setting the –Duser.timezone=<your_DB_time_zone> startup parameter in Java option used to start weblogic server.

-Duser.timezone=GMT

Note : You have to set the JVM timezone to the same timezone as the DB has! After setting the timezone, a complete restart is required to make the changes take effect.

In case of any ©Copyright or missing credits issue please check CopyRights page for faster resolutions.