This content has been marked as final. Show 14 replies
1. I am not getting HTTP 404 Error. its Unable to connect message from browser (As if the site is not available/ internet not working)
2. my link is http://localhot:7777/apex
3. Result of LSNRCTL STATUS
LSNRCTL for 64-bit Windows: Version 188.8.131.52.0 - Production on 09-NOV-2012 22:41:31
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))
STATUS of the LISTENER
Version TNSLSNR for 64-bit Windows: Version 184.108.40.206.0 - Production
Start Date 09-NOV-2012 22:25:42
Uptime 0 days 0 hr. 15 min. 51 sec
Trace Level off
Security ON: Local OS Authentication
Listener Parameter File C:\app\Bhatt\product\11.2.0\dbhome_1\network\admin\listener.ora
Listener Log File c:\app\bhatt\diag\tnslsnr\Bhatt-PC\listener\alert\log.xml
Listening Endpoints Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "krunal" has 1 instance(s).
Instance "krunal", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
If you're using the default database listener (and you haven't crafted your own listener.ora file, which I suspect you have not), do the following:
1) Connect as sys
2) Run: exec dbms_xdb.sethttpport( 7778 );
3) Run: alter system register
4) Exit SQL*Plus and then run your 'lsnrctl status' command again. See if the listener is now listening on port 7778.
5) If it is, try your URL again, but try on port 7778.
did the solution suggested by Joel work for your environment?
We have experienced a similar behavior with two customers, one running APEX 4.0.2.00.07, one 4.1.1.00.23 but both on 11gR2.
Restarting the listener only did not work - restarting the whole database instance finally did the trick.
Joel, thanks for the suggestion.
Do you have an explanation for this?
Many thanks and kind regards
Have you tried my instructions above? If the customer's database has a local listener defined (DB initialization parameter local_listener), you should be able to register the db with this listener using "alter system register".
I've seen this on my own personal DB - where the HTTP protocol doesn't seem to have registered with the listener. I've found that I have to do both - set the HTTP port and then re-register the listener. Do I have an explanation for this? No - it's beyond my domain of expertise.
no, we haven't tried your instructions yet, as the problem was solved by recycling the instance.
But we will certainly give it a try the next time this comes up.
We are currently investigating if there have been any changes prior to the outage.
At least it seems that the listener has been restarted and - like you mentioned - HTTP failed to register.
I will let you know if it works.
Just a small question though: Is it possible to set and register the original port (like 8080) again or is a different port required to fix this?
Thanks again and have a nice day,