Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: APEX in Oracle XE stopped working
On Wed, 15 Nov 2006 16:00:56 +0000, Martin J. Evans wrote:
> HansF wrote:
>> On Wed, 15 Nov 2006 01:37:45 -0800, Martin wrote: >> >>> The database is running fine - no problems there. Just this problem >>> with apex. >> >> Generic response here ... >> >> A few possible external factors may stop APEX from running. You don't >> specify which Linux you are using and that could make a difference as the >> distros have some differences.
Thanks. Fedora series is notable for the infernal SELinux interfereing with Oracle operations. However, you have verified that SELinux is disabled.
>> Another challenge is DHCP ... the listener & tns lock in the host name at >> install time and DHCP can change the host's IP so that does not always get >> resolved consistently. Similar symptoms from DNS-based resolution instead >> of /etc/hosts
$ORACLE_HOME/network/admin ... the listeer.ora and tnsnames.ora files.
>> What happens when you try going against the localhost instead of the >> installed host? http://localhost:8080/apex
Yup. Sorry , I'd glossed over the previous replies and missed that one.
This states, in no uncertain terms, that the apex listener is managing the intercept properly. That sort-of tells me the port and DHCP stuff is not an issue right now.
Which means that apex itself may have become invalid or corrupt.
http://{host}:8080/i should give a list of directories.
Suggest you register for the Oracle Tech Net (otn) Express database discussion forum and ask there. I haven't spent any time researching an Apex-only reinstall (as my specialty is the XE baseline install), but a few of the others have gone down this path.
Search this forum and the OTN Database-General forum for 'register for XE'
>
>> Since you can access using sqlplus, what happens when you >> >> exec sethttpport(8091); >> >> in sqlplus as a DBA, and then try http to that port in your browser.
I keep doing that ... it's dbms_xdb.sethttpport()
But ... it's not necessary in this case, as the listener is actualy running properly on the right port.
-- Hans Forbrich (mailto: Fuzzy.GreyBeard_at_gmail.com) *** Feel free to correct me when I'm wrong! *** Top posting [replies] guarantees I won't respond.Received on Wed Nov 15 2006 - 11:46:37 CST