ORA-01882: timezone region  not found - ORDS, SODA & JSON in the Database

I have installed Apex Listener with Tomcat 6 on Ubuntu. After I entered user/password and pressed Apply Changes button got the following error:
Request could not be processed due to error:
Wed Jul 07 11:22:28 UTC 2010
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
Please help 

Is there more in the log?
what version of the database?
what version of the listener?
An error with little context is hard to diagnose.
-kris 

Bumping this thread:
I am having the same problem with Apex Listener 1.1 EA running on Oracle 10g XE with Apex 3.2.1. The timezone I am using it CAT or UCT +2. This occurs during listener configuration.
Thanks
Edited by: timgaulza on 2010/10/25 5:35 AM
Edited by: timgaulza on 2010/10/25 5:44 AM 

I have the same issue with the following setup:
Linux Ubuntu Server 10.10
Oracle XE
APEX Listener 1.1 EA
GlassFish 3.0.1
Following is some entries from the server.log:
[#|2010-10-29T06:15:22.652+0000|WARNING|glassfish3.0.1|oracle.dbtools.apex.admin.AdminManager|_ThreadID=26;_ThreadName=Thread-1;|oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)
java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found 

Hello,
I'm just wondering if you have tried updating to the current version (1.0.2) of the APEX Listener? It has been released about two months ago and the EA-Versions probably have some bugs that have been fixed in that version.
If that doesn't help, perheps it helps to give your GlassFish your timezone via JVM-option (as described for GlassFish in this [url http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html]document), e.g.
-Duser.timezone=CETSet this to the same timezone your server is configured for.
If you haven't configured your servers timezone, it might be a good time to do that.
Just found another possible cause for your problem: The timezone data in the JDK you use. There is a updater for this, which is documented here: http://www.oracle.com/technetwork/java/javase/tzupdater-readme-136440.html
Note that the current version of the APEX Listener requires JDK minimum version 1.6.0_20.
I hope you get the Listener up and running properly.
-Udo
Edited by: Udo on 30.10.2010 01:31 

Udo...
You are amazing... thank you very much
it is working for me 

Hello Salim,
I'm glad to hear you got it working. Could you post which of the actions you performed to solve the issue? Just in case someone else comes up to this thread it would be nice to know... ;)
Thanks,
Udo 

Thanks Udo but this appears to make no difference to the CAT timezone, it seems to relate to daylight savings zones mainly.
I have attempted to running the embedded listener 1.1.0.291.08.34, to alleviate any third party interference, with no joy. 

I've added -Duser.timezone="+02:00" to my arguments which replaces the CAT timezone but retains the correct zone relative to GMT.
And it works! 

That's good news!
Have you tried the other option with the timezone updater tool? Perhaps this fixes the issue with the "named" timezone.
So I'm looking forward to hear if this solution solves the problem for Habib as well.
-Udo 

Udo,
I'm responding for timgaulza. We did try tzupdater with no luck.
BTW. Udo thanks for the help.
Edited by: Vis Naidu on 12-Nov-2010 17:13 

For Ubuntu Server 10.10 I used the following command:
sudo tzconfig
That worked for me. 

I had the same problem with sqldeveloper-3.0.04.34-1.noarch in Ubuntu, I edited the config file in /opt/sqldeveloper/sqldeveloper/bin/sqldeveloper.conf adding
AddVMOption -Duser.timezone="+05:30" (My time zone)
It worked for me. Thanks for the hint.
Harsha 

Hi All,
I added AddVMOption -Duser.timezone="+01:00" (my timezone) to the sqldeveloper\sqldeveloper\bin\sqldeveloper.conf file and it works. Thanks. 

Hi where you have added this..could you explain me clearly

Related

Password Sync on Windows 2008?

Does anyone know if Windows 2008 is supported for AD Password Sync on IDM 8.1? The doc says 2003 or greater, but 2008 is not mentioned. I have installed it and configured it, but see nothing going anywhere. Using direct method. No trace logs. No logs period. Nothing showing up in IDM. Any ideas?
Thanks, -T- 
Hi Tim-
IDM 8.1 definitely supports running passwdsync on Windows 2008.
The following is on page 31 of the 8.1 Rel Notes:
PasswordSync now supports Windows Server 2008 (32 and 64-bit versions). (ID-18342)
Did you reboot the Windows machine after installing the passwdsync DLL? Passwdsync logging is definitely what you'll want to take a look at.
Regards,
Alex 
Thanks for the info Alex. There is no logging. I set trace levels to 4 and there is no log file being generated. Is there an alternative logging method/place I should be looking at? 
You're welcome Tim. Just to be 100% clear, are you running the new 2008 "R2" release of Windows? If so, that's not supported until 8.1.1, which is scheduled to release (subject to change) next month.
Finally, if you are running 2008, can you confirm that you rebooted after installing passwdsync?
Regards,
Alex 
A couple more things: Can you also paste the actual Windows registry key for passwdsync in this forum so I can see all the parameters?
Also, which user is running the passwdsync service? Is it the LOCAL admin account or something else? You may want to see if that makes a difference.
Finally, how about the Windows Event Viewer logs? Anything in there?
Regards,
Alex 
A. The errors we are receiving on the Windows 2008 R2 Domain Controller are:
The description for Event ID 256 from source PasswordSync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The description for Event ID 257 from source PasswordSync cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
sbottle
?ailed to crack url 
I don't have my resources at the moment, but I know for sure that the passwdsync dll that comes with IDM 8.1 cannot install on Windows 2008 R2. 8.1.1 will have that capability, though. I am almost certain you're hitting a known issue. I'll verify tomorrow morning.
Regards,
Alex 
Hi again Tim-
Given the error "failed to crack URL" I believe you're hitting an issue we have documented as bug # 21999. Here's the jist of it and a possible way around it.
==========
When installing password sync on a Windows 2008 system, if you are not
logged in as 'Administrator', the installer and the configure applications
may be subject to Windows File And Registry Virtualization (FARV). This may
cause the registry entries for password sync to be written to the user portion
of the registry, rather than the system portion. Subsequently, password sync
will fail with the message "failed to crack URL".
To work around FARV, either run the MSI installer from a privileged cmd.exe
prompt, or run the configure.exe application using the "Run As Administrator"
functionality (right-click on the configure.exe application, select "Run As
Administrator").
==========
Hope this helps.
Regards,
Alex 
Hi Tim-
I was just wondering if the info I provided last week was helpful. If you have the chance, please let me know. Thank you in advance.
Regards,
Alex 
My customer decided to wait for the SP before we try to implement PW Sync. When we do go for it, I'll be consulting your notes. I do appreciate your responsiveness. Thank you very much.
Tim 
You're very welcome Tim. Thank you for the quick response.
Regards,
Alex

Problem with external resources

Hello,
We have upgraded Sun Identity Manager version from 7.1 to 8.1 and have now problem when an user (who had normally the capability) want to create, update, or delete user from external resources.
We had not that problem on 7.1 version.
When we create an user on an external resource, we have this error message :
"Error: com.waveset.util.WSAuthorizationException: View access denied to Subject 200044 on Configuration: External Resource Configuration. "
Anybody has ever seen that problem ? If you can help it would be great !
Thx
BJ
Edited by: Bjouannes on Dec 9, 2009 1:50 AM 
BJ, I have definitely seen that problem before. Would it be possible for you to apply the latest 8.1 patch (8.1.0.6) and see if that resolves the issue? I am almost certain it's a known bug.
The patches can be obtained here assuming you have the appropriate credentials: http://sunsolve.sun.com/show.do?target=patches/zp-Software_Network-Internet_Identity_Manager
Regards,
Alex
PS...You may also want to search these forum archives. I believe you'll find examples of others seeing the same issue. 
For the record, I believe it's bug # 21657.
Regards,
Alex 
Bug 21657 says that it's fixed in 8.1.0.6, 8.1.0.7, and 9.0.
8.1.0.7 has a target GA release date of 1/1/10.

Apex installation - Timezone Error.

Hello,
When Configuring Apex Listener 1.1 with Glassfish 3.1 for Oracle Database 11g R2 on Linux I got this:
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
How can be fixed?
Thanks, 
Hello,
you've run into a common configuration problem there. Two possible solutions have been discussed recently here:
{message:id=9413580}
{message:id=9413612}
If these don't solve the problem on your site, you may also read the rest of the thread for further approaches.
Hope this helps you get your APEX Listener running.
-Udo 
Hi,
I have followed the steps in the above link(they are referring to same content), but the issue still there:
ORA-00604: error occurred at recursive SQL level 1
ORA-01882: timezone region not found
my gf:
-Duser.language=en
-Duser.region=US
my db:
select * from nls_database_parameters
NLS_LANGUAGE
AMERICAN
NLS_TERRITORY
AMERICA
Could you please advise? this is preventing me from accessing the application after this 1.1 install.
thanks, 
Hi,
the second link was indeed a different message of the same thread.
It seems, the timezone you have configured for your OS is still unknown to the database. You could try to set an additional Java option for the timezone-equivalent for the one you are using, e.g.
-Duser.timezone=CATI found a different thread discussing that special option: {message:id=8475026}
We also tried to use the timezone update for Java (*tzupdater*), to set the timezone not by name but by value (e.g. -Duser.timezone="+02:00" ), or by just generating appropriate timezone data at OS level (*tzconfig* on a linux machine).
I'm sorry I didn't post the link to that thread in my first response, as I originally wanted to - must have copied the value from the wrong browser tab, but as message ids differ, I didn't see the fault.
Hope this solves your problem now.
-Udo 
Thanks mate, worked well. 
Great!
Could you mark this thread as "answered" and assign answers as helpful or correct to make it easier for other users that search for this issue to find the relevant posts.
Thanks,
Udo 
Done, thanks alot.

Changes in 1.1.2

Thanks again for all your feedback on 1.1.1, we have addressed a few more issues since 1.1.1
<ul>
<li>Reduced the default value of apex.jdbc.MaxConnectionReuseCount from 50000 to 1000. This may address issues with the database temp segment being exhausted (Error ORA-01652). There were problems with this fix in 1.1.1, it is fully fixed in 1.1.2</li>
<li>Fixed a problem with the standalone Listener where the location of the images folder could not be overwritten.</li>
<li>Removed obsolete cache.dir parameter from web.xml. Use the apex.cache.directory setting instead (in apex-config.xml)/li>
<li>Removed obsolete apex-config.xml in the distribution zip file</li>
</ul>
If you are using the Listener caching facility please ensure you use 1.1.2, and note that the cache location can only be configured via the administration screen (or by editing the apex-config.xml setting named: apex.cache.directory)
Download here
Edited by: Colm Divilly on May 11, 2011 10:58 AM 
Hi Colm,
I can confirm all four points to be fixed - good job!
Once again, it's great to see how fast bug fix releases for the APEX Listener are published. Of course, the Listener is comparatively lightweight - I hope you can maintain this lightweight release process, and I appreciate the personal efforts you doubtlessly put into that product.
Thanks!
Udo

I can't see server on Admin GUI

After installation Sun Ray Software 5.2, I can not see my server on Admin GUI.
The SERVERS tab is empty. It only shows:
Servers
This page lists all Sun Ray servers with the same group signature. Click on the server names to display additional details. More on Servers. 
There is a bug in the CSS of the Admin GUI which doesn't display the "content" of the server or sessions register site in Firefox 4.0/5.0 and IE9. There is an unofficial workaround http://www.collectivesystems.com/blog/stuart/entry/firefox_4_and_the_sun which makes the CSS valid again for those new browsers.
Support will say, please only use supported browser like Firefox 3 :-) 
Be aware of that this artice was written after the release of SRSS 5.1. In 5.2 the GUI changed to Oracle branding. The problem perhaps could still be the missing CSS entry. I would insert it manually :-) 
Actually IE9 works just fine. It's the other major browsers that the page doesn't work with. 
I use this fix anywhere, even in SRSS 5.2.1 with FF5. Works nice ...
regards, thomas 
Hi,
Been looking at this issue and the link of Stuart Robinson which is mentioned in the thread does no longer exist.
There is an Oracle Support note however which covers this problem: (note with id 1351146.1 dd 2-sep-2011, defect no 12362196)
The note mentionnes that the bug will corrected in a future release ... only it does not state when.
Neither can I find the 'defect' with number 12362196.
In the mean time, and as a lot of people are not IE to administer the sunray infrastructure, a good idea to document the correction publicly ...
Greetings,
Jan. 
Hi Jan,
That Knowledge doc has just been updated to say that this is fixed in SRS 5.3.
Regards,
Ryder
Edited by: DoesNotCompute on May 8, 2012 12:02 PM 
Oh Great!!!
Downloaded, installed and working already ...
It is indead fixed ...
To upgrade the DTU's, need to download a separate file from support and install it before you install the SRS soft ... just not to forget.
Greetings and thanks for the message, Ryder!!!
jan;

Categories

Resources