Cannot access apex app from google Chrome - Oracle Database 11g Express Edition Beta(Archived)

I just installed the long waiting 11g Xe, the installation is ok, but I have a problem accessing my app from google chrome, it prompted a pop-up box let me input login infor for XDB.
I don't know why, other browsers like firefox is ok, no this kind of problem. 

Well, if it works on other browsers then the problem might be with Chrome.
I would get an login prompt (on IE 9) if I tried to open incomplete url instead of or 

Hi all,
Today I run into the same problem when playing around by switching the theme of the sample application.
Google Chrome prompted to login for XDB when rendering a page.
No problems before switching the theme.
Excellent combination Oracle 11 and APEX 4.0 in one package.
Best regards,
Martijn Peters 

Thanks for the reply, and I also hope it is a google chrome issue, and I am using the beta version of chrome, but I like this browser very much, it is fast and quite a lot of functions, do do some work and making sure it goes smoothly with google chrome.

Yesterday I installed XE 11g beta on XP Pro SP3 with Google Chrome as default browser. Used Chrome as browser for APEX and everything working perfectly.
Probably your issue is connected with beta version of your browser and/or browser settings. 

I had the same problem when I started using Oracle Express 10g and APEX, and I found the solution in this thread: <a class="jive-link-external" href=""></a>
More specifically, to avoid getting the XDB login prompt you have to enable anonymous access to the ML DB repository. You can do that by using the following code which creates the "<allow-repository-anonymous-access>" element if it is missing, or updates it if it is already present in the xdbconfig.xml file.
CONN sys/password AS SYSDBA
l_configxml XMLTYPE;
l_value VARCHAR2(5) := 'true'; -- (true/false)
l_configxml := DBMS_XDB.cfg_get();
IF l_configxml.existsNode('/xdbconfig/sysconfig/protocolconfig/httpconfig/allow-repository-anonymous-access') = 0 THEN
-- Add missing element.
SELECT insertChildXML
XMLType('<allow-repository-anonymous-access xmlns="">' ||
l_value ||
INTO l_configxml
FROM dual;
DBMS_OUTPUT.put_line('Element inserted.');
-- Update existing element.
INTO l_configxml
FROM dual;
DBMS_OUTPUT.put_line('Element updated.');
/Hope this helps (and thanks to <a class="jive-link-external" href="">Pravednik</a>, the user who posted this code originally),
Edited by: srecio on Apr 6, 2011 9:22 AM 

Enabling anonymous access to XML DB repository can be security risk.
XDB login prompt don't appear if browser get the right URL: - for XE 11g Home
and - for APEX Login
Hope this helps. 

You're right about the security issues, as the Oracle documentation says, but I simply suggested that solution in case Yawei was just doing some tests and to avoid the problem in Google Chrome.
Kind regards. 

Hi Guys,
thanks for your rplies, and I will try your method later!
I have tried the sample app in chrome, it is working perfectly, no pro.
But my apex app was developed under a lower version of apex, 3.2. maybe some configuration is wrong when installing it in the latest version.
but it works perfectly at my current 10gxe/apex4.0 environment, any way, firefox is ok for me. 

Hi Srecio,
I have tried the code you offered, and it worked,that is very good! thanks.
Maybe it is not very secure, but it is a app used mainly in our local network, security is not a big issue.


Getting blank page using APEX Listener in standalone mode

We are getting a blank page when using the APEX Listener in standalone mode from 64-bit machines (Linux, Unix, or Windows), but it works when the apex.war/APEX Listener is launched from a Windows XP 32-bit machine.
Help, please!
Oh, and I can get to listenerConfigure, then listenerAdmin, but not to apex/apex or apex/apex_admin 
Question appears to be more appropriate for the +{forum:id=858}+ forum. 
Hello Alex,
I had no problems on either Win 7 64bit or Ubuntu 64 bit to get the APEX Listener up and running in standalone mode. However, you have to make sure you meet the JDK requirements described in the Installation Guide (JDK 1.6.0_20 or higher). Another aspect could be the firewall to the database. Is it allways the same database and are you able to connect to it from the 64bit boxes, e.g. using SQL Developer?
Do you see any kind of error message on the 64bit systems? The console output might help to get a clue on what's going wrong on your 64bit systems...
In our Windows 7 64bit machine, our java -version is 1.6.0_29. In our RHEL 64bit machine, it's 1.6.0_20.
There are no errors in the logs. We can actually do View Source on the blank page and we see HTML code.
It is the same database behind our firewall that we can access via SQL Developer, etc. Both the Windows and RHEL machine sit behind the firewall, too.
It's working for our Windows XP 32bit java 1.6.0_25 machine. 
BTW, this is how we are launching the apex.war app, in case it's helpful:
java -Dapex.images=/pcm/apex_home/images -Dapex.port=8070 -Dapex.home=/pcm/apex -jar apex.war
The listener is starting Ok. We can see the code behind the blank page. It just seems that it can't find the "/i/" directory, but we are indicating were the images directory is, and we've confirmed that the files exist 
BTW, this is how we are launching the apex.war app, in case it's helpful:
java -Dapex.images=/pcm/apex_home/images -Dapex.port=8070 -Dapex.home=/pcm/apex -jar apex.warIt helps a bit. Combined with the fact of the unresolved "/i/" directory it might be a problem to be solved soon, as it would explain the symptoms you see. Now, let's try to track it down:
Please check whether +/pcm/apex_home/images+ is readable for the user/group you use to start the APEX Listener. Also make sure it actually contains the images that correspond to the APEX version you are trying to access and that the APEX instance is configured to use "/i/" as Image Prefix.
What kind of result do you receive when you simply call
This call should work if you have configured the right directory with proper permissions. If it doesn't: How did you create the contents in you apex.home +/pcm/apex+ ? Did you copy it from an initial installation? If you use an older version of APEX Listener, you may encounter the problem that the command line parameter apex.images doesn't overwrite an existing old value in the in the apex.home , so if you previously configured your APEX Listener to use a different images directory, it might still try to use that directory. To solve that problem, you should use the most recent release of the APEX Listener. (It would have been a good idea to post the version you are currently using anyway...)
This issue was resolved. Our images folder was missing some images, which I still can't explain how that happened, but it is what it is, as dumb as it sounds :-(
Thank you for your help!
BTW, we are having another issue, but we'll open a separate thread to see if we can help with that one.
Thanks again,
It doesn't sound dumb, it sounds more like everyday business. I'd recommend to use Firebug or similar - it makes detecting issues like that much easier.
Anyway, the most important thing is you're now able to use APEX Listener (again).
Please mark this thread as answered and mark helpful or correct answers so others coming by can spot relevant post easily.
I had similar issue with Standalone Apex Listener on AIX deployed as follows :
/usr/java6_64/jre/bin/java -Dapex.home=/opt/oracle/v11.2.0/Apex4.1/apex_listener/standalone_listener_basedir -Dapex.port=8080 -Dapex.images=/opt/oracle/Apex/images/apex4.1.0/images -Dapex.erase=true -jar /opt/oracle/v11.2.0/Apex4.1/apex_listener/apex.war
After attempting the actions detailed in this thread, i still had no success, however the advice given sent me in the right direction
Turns out my problem was the path to the images directory that I'd specified within my java deploy
- It needed the trailing slash !
that is : -Dapex.images=/opt/oracle/Apex/images/apex4.1.0/images as initially deployed failed
where as -Dapex.images=/opt/oracle/Apex/images/apex4.1.0/images/ worked

2.0 Listener on Apache Tomcat

need your help. Trying to run 2.0 Listener on Tomcat 7. Was running 1.1.4 before and everything was working perfectly fine.
Did configuration per manual. When trying localhost:8080/apex I'm redirected to normal url (kind of http://localhost:8080/apex/f?p=4550:1:3416114183042) but the result is absolutely empty (not the page, but result in "view source"). Tomcat logs show normal HTTP 200 code returned.
Can see open sessions in DB by APEX_PUBLIC_USER and APEX_LISTENER - looks like everything is fine here.
Any idea?
Forgot - Apex 4.2. Upgraded from 4.0. After upgrade everything was working perfectly fine with 1.1.4 Listener, so my guess - this is something related to 2.0 listener itself... 
Forgot - Apex 4.2. Upgraded from 4.0Are you sure you've copied the new images for APEX 4.2 to your Tomcat? If so, do you use a war file to deploy them or do you use the ROOT-context to serve static contents?
After upgrade everything was working perfectly fine with 1.1.4 Listener, so my guess - this is something related to 2.0 listener itself...How much time (and how many restarts of your browser and Tomcat) had been between these two events?
Thanks for you answer, Udo!!!
Images are definitely there. As I said - 4.2 was working perfectly fine after the upgrade and new images deployed to the server.
Also, whenever I had problem with images before - there were problems with the page, but there was SOMETHING returned. Here - absolutely empty page (no source at all). Though http 200 return code.
As for time between these events - all happened the same day. We upgraded to 4.2. Deployed new images. Confirmed everything is working fine. Start playing with 2.0 listener... 
Missed images deployment question - we used war file for deployment But we deploy to ROOT - not under apex. And this is how it was always before... 
Still trying to figure out what is going on...
In one of APEX_PUBLIC_USER active sessions I found SQL like this:
msg varchar2(100);
msg := dbms_java.endsession_and_related_state;
I'm not 100% sure, but I believe dbms_java.endsession_and_related_state is defined in 11G. We are on Am I missing something? 
Getting more and more interesting :-)
If you wait long enough (20-30 minutes) and refresh the browser on the same url, that was giving absolutely blank screen before (http://localhost:8080/apex/f?p=4550:1:3416114183042) - you are getting perfect login screen! All the images are fine, everything looks great. But if you try to login - getting absolutely blank screen with the url of below:
And yes - I used wrong id/password when trying to login.
Any idea? 
OK, tried to rollback to 1.1.4 version and as expected everything is working perfectly fine.
With 2.0: Very strange - if you leave browser for 20-30 minutes on the same initially absolutely blank page and refresh - you get correct result. And after you login successfully - you have kind of regular admin screens without any delay or blank screens. If you logof - same story. Blank screens, keep them for 20 minutes alone, then refresh - you are in.
When I said "kind" of regular screens - any screens, that have interactive reports, show error "there can be one interactive report per page". And just to confirm: when we rolled back to 1.1.4 - same screens worked perfectly well.
I'm lost 100% and hope only that sooner or later some Tomcat/Listener/Apex gurus can help me :-)
Meanwhile - back to 1.1.4 working version... 
I installed Apex Listener 2 on Tomcat 6.0.33 by this instruction Apex 4.1. All works perfectly. 
Thanks for your report,
there is a regression in Listener 2.0.0 that causes APEX not to work properly on 10.x databases. We will release a patch release of 2.0 to address this (and other issues reported in this forum) in due course. The problem does not affect 11.x databases.
Edited by: Colm Divilly on Feb 8, 2013 7:45 AM 
Thanks a lot for the update!
Any info on when can we expect the fix? Just roughly - need to know to plan for our company accordingly... 
We are also interested in:
(a) whether or not the patch/fix for APEX Listener 2.0 with DBMS 10g has been completed; and
(b) (if not) what the current ETA for said patch is.
(c) What the relevant links (tech notes, bug #'s, etc.) are for monitoring progress on this issue.
Thank you
Edited by: MarkB on Apr 11, 2013 10:28 AM 
The 10.2 regression was fixed in 2.0.1 which was released March 2013, the list of fixed issues is here:
(the 10.2 issue is the first one listed).

Question regarding System Requirements for 2.0

The below link to the System requirements for the 2.0 listener state that Microsoft Internet Explorer 8 or later is required. Why is this?
Surely if configuration is done through SQL Developer or the Command Line, there isn't a specific browser requirement? Surely the listener is a server side component, is anyone able to enlighten me?
Edited by: RichDBA on Jan 2, 2013 3:40 PM 
In my opinion are 2 reason:
1. IE 7 and lower have many many bugs.
2. Apex Listener 2.0 has own Error pages, probably this pages can't work or not correct work with IE7 and lower.
When you say its own error pages, do you mean pages presented for HTML status codes, such as 404 and 501 etc? If so, then I guess that could be the case, but I can't believe that those pages would be so advanced that they don't work in browsers earlier than IE8.
We currently use IE6 in our enterprise environment (soon to be moving to IE8) so I was really hoping to find out if I could get by with IE6 for the short period before we change over.
Is anyone out there using the 2.0 listener with browsers older then IE8, are you experiencing any issues?
Hi Rich,
I didn't test AL 2.0 with IE 6, but I don't see a reason why this shouldn't work. I think this requirement has been forwarded from APEX Listener 1 (and 1.1, respectively), which has a web based admin GUI that used CSS features IE 6 didn't implement. Possibly the current error pages may not appear well formatted if you view them in IE 6, but I don't think this would be a no-go for production.
You shoul keep in mind, that current APEX releases require at least IE 7 to work properly, at least with themes provided by these releases. But if you don't experience any issues with your APEX release, using APEX Listener 2 instead of your current web server for APEX won't make any difference.
Thanks Udo,
I had assumed that it was possibly a hangover of the previous version that was configured via the browser. I think based on this information I'll push ahead with my implementation.
Rich install change? IE8 non-functioning now

2 weeks ago, Downloaded all the files, ran through an install and had no problems.
same thing this weekend, except now, I cannot get IE8 to render workspace at all. Ive followed all the steps on this:
     Internet Explorer (IE7, IE8 and IE9) Recommended Settings for Oracle Hyperion Products [ID 820892.1]
Everything, and I mean everything is set to 'low' in security settings, and enabled.
However, I installed:
and I can get everything to render just fine in firefox...
Anyone know what recently changed?
Can you check the java version on your machine, i have seen this causing issues.
Any java 1.6.xx should be ideal 
Try to clear the browser cache and RESET the IE settings and then proceed with the support document and set the browsers as required and see if that works.
Please mark answers as helpful or correct for others to find them easily. 
I can do you one better.
I actually created an amazon instance with the sole purpose of trying to connect - I set everything to be 'low' security setting wise, and there literally is no cache to clear. since I had never loaded a web page before, and I added every server onto the intranet option. Only firefox works after installing that plugin.
I tried 3 java versions.
Did you try resetting the IE settings and then trying it again?

Deployment stuck at "Connecting to database...." at Unifier login page. Login button disabled

I've been working on deploying the 9.13 version of Unifier. Everything stood up fine, however at the Unifier login screen, it shows "Connecting to Database..." above the username and password entry forms, and the Login button is disabled and I cannot proceed any farther in the setup. Checking the SQL tabular view, the DB is empty. Can anyone point me as to where I might have missed a step?
Hi, It sounds like you are running into a known bug (although it says it was fixed in it might have still found it's way into Let us know how you go with the following steps:1. Stop the Unifier web server instance.2. Navigate to the [Unifier Installation Home]\apps\ROOT\WEB-INF\classes directory and open the file in a text editor.3. Update the server= line to include the name of the Unifier database in the databaseName= portion. Also remove the portion after the databaseName= portion. Example before change:  server=jdbc:sqlserver://localhost\:1433;selectMethod=cursor;databaseName=;selectMethod=cursor; Example after change (database name is unifierdb): server=jdbc:sqlserver://localhost\:1433;selectMethod=cursor;databaseName=unifierdb;   RegardsAlex
I had this issue as well installing Unifier 9.12, I worked out that it was the version of JDK I had selected. When I installed WebLogic Server 11g it asked me what version of JDK I'd like to use and I chose one of the versions that was bundled it with it. After having no luck I ended up download JDK 7u25 and reinstalled WebLogic, this time when it asked me what version I wanted to use I specified custom location and pointed to the path of JDK 7u25, once I got the deployment stage the login window now connected to the database and I was able to login. Zac
Thanks for the info. Solved this last week. The problem I was hvaiong was I was using the 32 bit WebLogic install on top of the x64 Java base.One would think it would give you a nice error on compatibility but no it loaded fine apart from that functionality issue. Thanks for relating your experience as well. Hopefully someone else won'ty make our mistakes haha