New VSE setup - Shuts down shortly after starting reporting DB connectivity issue

Document ID : KB000072243
Last Modified Date : 27/02/2018
Show Technical Document Details
Issue:
I have a new vse I am connecting to an existing registry. Shortly after starting the VSE stops and the vse log reports DB connectivity issues. The registry I am connecting the vse to has other VSE successfully connected. The logs are providing me with enough information for me to determine next steps. vse.log attached. This could be a firewall or port issue, but I have validated all the ports I am aware of.
Environment:
All Supported DevTest platforms and Releases.
Oracle database.
Cause:
The Registry, VSE and Oracle database are all in the same time zone, the VSE having the issue was not.

The VSE log in error showing this message:

Thread-#2] DEBUG com.mchange.v2.resourcepool.BasicResourcePool - An exception occurred while acquiring a poolable resource. Will retry. 
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 
ORA-01882: timezone region not found 

 
Resolution:
Added this property in the local.properties file on the VSE machine seems and it resolved issue which indicates this is an Oracle issue.

oracle.jdbc.timezoneAsRegion=false

TZ of the machine of where your Registry is running? Time zone: America/New_York (EST, -0500) 
TZ of the machine of where the VSE that did not have a problem? Time zone: America/New_York (EST, -0500) 
TZ of the machine of where the VSE that did have the problem. : Time zone: Etc/UTC (UTC, +0000) 

Need to set TZ of where the VSE that did have the problem to be America/New_York (EST, -0500) 

Setting the TZ of the VSE having the issue resolved the problem.  Was able to remove the oracle.jdbc.timezoneAsRegion=false property.
Additional Information:
https://support.solarwinds.com/Success_Center/Database_Performance_Analyzer_(DPA)/ORA-01882_Timezone_region_not_found_error_when_you_try_to_register_an_Oracle_database