This content has been marked as final. Show 14 replies
Firewall isn't relevant when using loopback (127.0.0.1) IP address.
switch off the windows firewall
Step One, make sure your database is running. Might need a service start. In a command box:
Step Two, make sure your listener is running, back to the command box:
sqlplus /nolog connect system ... password: <use the one set in the install> ... Connected. -- Or ... maybe not. Try starting it: conn /as sysdba; ... Connected to idle instance ... startup;
Step Three, check that `lsnrctl status` command output, you should have two endpoints, the database default 1521 port, and the 8080 web page port. If the 8080 port isn't in the lsnrctl output, the web pages will not work.
lsnrctl status ... Endpoints: ... 1521 ... ... http ... 8080 ...
That .jpg URL won't render for me. Anyways ...
"seems like" and "actually are" could be two very different things, connecting to the database to ensure it is running and the lsnrctl status command are ways to check and verify.
it seems like everything is up and running
In Windows the service can be running but a sysdba connection to the database instance can shut it down and the services won't show any differently. Or the instance could crash, still won't see any differences in the services list.
I don't know if you got my previous reply, it seems like this forum is experiencing some issues today, I don't see my reply, that is why I'm sending you back the last image I capture just a few minutes ago, also I'm sending you yesterdays image (the one you couldn't open)
maybe this is a dumb comment, but my computer has a static IP address within my works network which is 10.10.10.21 (don't have a clue if this could be trouble or not.....)
yesterdays image of win services
Edited by: 995397 on Mar 22, 2013 8:56 AM
Ahhh got the .jpg now. Can see you do indeed have two endpoints, but one of those is the ipc, its not relevant. IPC a.k.a. Inter-Process Communication is a host-only protocol and has no direct effect on networking.
And there is no http ... 8080 end point, so yes, the web pages aren't going to work.
Actually a static IP is preferred for a server- don't want it to have a different IP every time it boots as can happen with DHCP.
my computer has a static IP address
What is important, is the host= part. It can be the hostname, but it must be the correct hostname. Depending on how the network client is set up, it may not be.
And the Service ... instance "xe" status BLOCKED doesn't look good, could be the host= needing adjustment causing that.
Try stopping the listener, set the listener.ora HOST= to your static IP, or slightly easier, the "any IP" address of 0.0.0.0, start the listener, connect to the database, and force a registration. Back to the command box, the file that needs the change is listed as the "Listener Parameter File" in the lsnrctl status output:
When changing a listener.ora setting be sure the listener is not running, the HOST= tells lsnrctl what address to talk to for controlling the listener.
lsnrctl stop ... notepad <drive: ... >\network\admin\listener.ora ... change: HOST=BERNIE ... to: HOST=0.0.0.0 ... save and exit, start the listener lsnrctl start ... connect to the database and force it to register sqlplus /nolog connect system ... password ... Connected. alter system register; ... exit ... check listener status again lsnrctl stat
Edited by: clcarter on Mar 22, 2013 12:17 PM
add 2nd lsnrctl stat
Well, if you want the really really easy GUI way, in the services applet hit the Stop button on the OracleXETNSListener service.
Bring up the file explorer and navigate to your C: drive, open the oraclexe folder, and go way way down until you get to the ...\network\ADMIN folder.
Right click on the listener.ora file, hit Rename, and change it to something different- "listener.ora.bak" or something that is not "listener.ora".
Back to the Services applet, hit the Start button on OracleXETNSListener. It might take a minute, maybe two for the database to get re-registered with the listener. The sqlplus ... connect system ... alter system register; will shorten the wait time a bit.
And a helpful tip for the command box, do a right click the "c:\" icon in the upper left corner, click Properties, go to the Options tab and check the "Quick Edit" checkbox. That will let you use the mouse to highlight text in the box, press the Enter key to copy it to the clipboard. Much easier than posting .jpg screen shots ... ;)
Sorry for my delyed answer.
I tried everything without any luck, the problem must be somewhere else, I repaired the installation, unistalled the software and reintall it again, no luck, cannot log into the web app
I thing I will give up and look for another option, maybe my SQL will make it easier for me ?
thanks a lot !
Maybe. If desktop admin task skills are elusive, maybe not. MS Sqlserver express edition is another "free" database option, it has several prerequisites that the installer usually gets loaded to the desktop OK, if you have admin rights on the desktop.
maybe my SQL will make it easier for me ?
Everything? Stopping the listener, moving/renaming the listener.ora file is not that hard to do.
I tried everything without any luck
To stop the listener in the GUI, the services applet should be available via Start/run/services.msc look for the "OracleXETNSListener" service. Click it to highlight, click the Stop button.
Next try the "windows explore" utility or what ever its called in your particular host. The path is Start/Programs/Accessories on XP, for win7 the path is ... slightly different. Its the program with a folder for an icon.
Open up your C: drive, the oraclexe folder, and start digging. The full path to the listener.ora file is shown in your lsnrctl status output, labeled "Listener Parameter File". With that file moved out of the way the Oracle install has a default listener configuration that usually works better, especially if anything is wonky with the networking configuration.
After moving the listener.ora file, go back to the Services applet and click Start on the listener. In a command box (Start/Run/cmd) check the lsnrctl status output again. Might see a difference, and when the database instance gets registered with the listener that should get the 8080 port showing up in the lsnrctl status output.