Ensure the hostname and IP values are correct ...
lsnrctl stat ... ... lsnrctl serv tnsping xe ... used parameter file c:...network\admin\sqlnet.ora ... ... attempting to contact ...HOST= ... PORT= ... CONNECT_DATA ... SID= ... # could be SERVICE_NAME= instead of SID= OK (<n> msec) # or could be a TNS-n error ... hostname ... <hostname> nslookup <hostname> ... <hostname> ... <IP address>
Doesn't look like an XE install, perhaps another oracle install (client? rdbms server? something else?) has been installed since XE? Although lsnrctl appears to be the 10g version. Been a while since I've looked at a 10g XE, I guess 10.2.0.1 is the right patch level.C:\dw\server\trunk\server\source\..\..\appserverinstance\sharedata\config\oracle\sqlnet.ora
Try the trace ...=user first, and in the trace directory after trying the sqlplus ... conn ...@xe and see what you get, =user trace won't be too much verbage, but there should be something helpful.
# logging stuff TRACE_LEVEL_CLIENT=user #TRACE_LEVEL_CLIENT=admin #TRACE_LEVEL_CLIENT=support TRACE_FILE_CLIENT=sqlnet.trc TRACE_DIRECTORY_CLIENT=c:\temp
Doesnt work: sqlplus <username>/<password>@XE
That's two different problems. And firewall is not relevant for a localhost 127.0.0.1 connection. Getting apex to work depends on the correct network client setup, as well as having the database up and listener running.Still cannot bring up database home page http://127.0.0.1:8080/apex
That verifies there is a listener using port 1521, is it the correct listener? And hostname, "DW-CMILLEY5" ? That can prevent the apex service from working with the database. And could be its not the XE listener. From earlier, the lsnrctl status output:netstat -ab ... TCP 0.0.0.0:1521 DW-CMILLEY5:0 LISTENING ... tnslsnr ... seems like listener is connected
Your tnsping was hitting a different path, must be other oracle installs on the host. On linux for multiple installs, its not too tricky, but you do have to set up the environment to the correct $ORACLE_HOME, adjust $PATH, and $ORACLE_SID as well before doing anything with the database and listener.Listener Parameter File C:\oraclexe\app\...\NETWORK\ADMIN\listener.ora
There's nothing saying you can't run more than one listener on a host. But there is a rule that you can't have two (or more) listeners running using the same port, and the default 1521 port is what you get if the port is not specified in the listener.ora configuration.
lsnrctl stat ... Parameter File ... ... set ORACLE_HOME=c:\oraclexe\... set PATH=%ORACLE_HOME%\bin:%PATH% lsnrctl stat ... sqlplus /nolog connect system ... password ... connect ... @xe ... ???
Could be. How many NICs on the host? An ethernet port, or two? Plus maybe a wireless card as well? A command box ipconfig /all might show some clues on the NIC setups. A `netstat -an|findstr /i tcp` should show all the open tcp connections, `netstat -an|findstr /i listen` should show any ports with any type of service or program using the port. 1521 should be in there, will be a few others, like 139 (netbios?).some kind of problem with the port or network
Really? There's only one per client setup, and every client should also have a sqlnet.ora. And the application client(s) are pointed to the different tnsnames files how? With seting TNS_ADMIN environment variable?multipe tnsnames.ora files
xe1 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = n.n.n.n )(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = XE) ) )