TriniDBA

Problem:

While trying to connect to an Oracle 9.2.0.3 database on EBS 11.5.9 (running on Red Hat Enterprise Linux AS release 4) using SQL Developer 3.0.04, the following message appears:

An error was encountered performing the requested operations:
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
OO604. 00000 - "error occurred at recursive SQL level %s"
*Cause: An error occurred while processing a recursive SQL statement 
(a statement applying to internal dictionary tables).
*Action: If the situation described in the next error on the stack 
can be corrected, do so; otherwise contact Oracle Support
Vendor code 604

Solution:

Change the timezone variable in sqldeveloper.conf to a valid one for the database.

In SQL Developer, click the Help menu, and then click About.  In the About SQL Developer dialog box, click the Properties tab. Scroll down to the end of the list. user.country is set to ‘US’ and user.language is set to ‘en’, so neither of these two values were changed. I then checked user.timezone property. On my system, it was America/La_Paz.

Next, connect to the database (perhaps by logging on to the server via PuTTY or VNC) and query the V$TIMEZONE_NAMES view for valid values:

SELECT *
FROM   V$TIMEZONE_NAMES
WHERE  TZNAME LIKE 'America%';

From the rows returned, select a valid timezone name that is in the same timezone shown in SQL Developer properties. In my example, I used ‘America/Santiago’.

Edit the sqldeveloper.conf file (sqldevelopersqldeveloperbinsqldeveloper.conf) and add the following line:

AddVMOption -Duser.timezone=America/Santiago

Save sqldeveloper.conf, exit SQL Developer and then reload.

Reference:

https://forums.oracle.com/forums/thread.jspa?threadID=2256101

https://forums.oracle.com/forums/thread.jspa?messageID=9630177

https://forums.oracle.com/forums/thread.jspa?threadID=2196497

[amazon asin=1847196268&template=iframe image&chan=default]     [amazon asin=0071484744&template=iframe image&chan=default]    [amazon asin=0137142838&template=iframe image&chan=default]