This content has been marked as final. Show 8 replies
Is there any chance that the URL you use to login to Application Express is different, somehow, than the URL used to run the application?
I saw an occassion of this recently, where someone said that after they logged into their application, the developer toolbar disappeared. It turns out that they were logging into the APEX instance with a URL with a /pls/htmldb Database Access Descriptor. Then, they would run their application, get redirected to the Login Server, and then get redirected back to the same APEX instance but with a URL with a /pls/apex Database Access Descriptor (both worked).
Here are the URLS when the login pages are displayed, waiting for credentials:
And here are the URLs after I have logged into the application and into Application Builder:
Everything has "http://ah9.appshosting.com:7780/pls/apex/f?p=" in common.
Does this answer your question or give you a direction to look?
I wouldn't know about other APEX instances. We're an ISV and they host our development. The problem instance was upgraded a week ago, and I just started work on it last night. Discovered the problem today. They haven't responded yet. If there is no way to diagnose what's happening, since it's a dev env, they may want to drop APEX and do a clean install. That might be the only option.
You inspired me to take a closer look, and look beyond the upgrade.
After the upgrade, my application passed a superficial checkout. Later, I exported my application and in the export file, the Instance ID was not NULL. I had not noticed any problems with how APEX was working.
The problems of the missing Developer Toolbar, Instance ID = NULL, and a new one, did not occur until I removed my application and tested a clean installation of the workspace and application. This is the sequence of events. The immediate triggering cause is clearly one of the following:
1. Deinstall application (ID 820) from APEX 4.2.1.00.08 instance, running 11g (184.108.40.206.0).
2. Remove workspace (PVA_AH9_R12)
3. (drop the parsing schema, xxpva, and related tablespace)
4. (create tablespace and schema user, xxpva)
5. Import workspace (PVA_AH9_R12) from an APEX 4.2.0.00.27 instance.
6. Import application (ID 820) including supporting objects from an APEX 4.2.0.00.27 instance, running 11g (220.127.116.11.0).
The next day I noticed the Developer Toolbar missing problem, and found that Instance ID is NULL.
Also, after Exporting an application in Database format, I cannot download the file from the Export Repository. When I click the filename link, I get 'Access Denied' instead of the normal download dialog.
Does this suggest anything else I should look into?
Do you think I should post this as a new problem/question with more detail about the sequence of events?
If you're talking about the header of the application export file, where there is a line like:
-- Instance ID: 69332573836388
I don't believe this would have any bearing on the display of the developer toolbar in your application.
It is disturbing that you get Access Denied when attempting to download your application export (when exporting to Database format). Have you reported these issues to your provider?
Problem was caused by upgrade. The wwv_platform_prefs file changed the security_group_id. This led to the problems with the developer toolbar and access denied to files in export repository.
See My Oracle Support patch number 16270085, which fixes the platform prefs table.
Thanks to Joel for sorting this out and fixing it.