Saturday, September 26, 2015

XE Database Listener failed to start

XE Database-Listener Start Error

[oracle@localhost ~]$ lsnrctl start



System parameter file is /u01/app/oracle/product/11.2.0/xe/network/admin/listener.ora

Log messages written to /u01/app/oracle/product/11.2.0/xe/network/log/diag/tnslsnr/localhost/listener/alert/log.xml


TNS-12555: TNS:permission denied

 TNS-12560: TNS:protocol adapter error

  TNS-00525: Insufficient privilege for operation

   Linux Error: 1: Operation not permitted


Listener failed to start. See the error message(s) above...



I was setting up SOA 12c environment on my personal laptop and thought of giving it a try with oracle 11g XE database. Mind it that Oracle XE database is not officially supported for SOA 12c. Though the installation of XE database was damn easy, setting up of remote DB connection (using tns method) left me quite a bit frustrated.



The initial connection after the XE setup using tns method was successful, but once I restarted my laptop, subsequent tns connections were failing complaining about listener unavailability. On restarting the listener I received the error shown above.


What didn't work?

I tired many things, like assigning ugo+rwx to oracle home, starting the listener using “sudo service  oracle-xe start” but none yield any good results.



It was after some trials I realized, that to have listener (and DB) running properly, following must be ensured:

a. “lsrnctl start” should be executed by root user only and not with oracle (oracle software owner) user

b. “sqlplus> startup” should be executed by oracle user only




[root@localhost ~]# lsnrctl start


LSNRCTL for Linux: Version - Production on 18-NOV-2015 20:34:46






Alias                     LISTENER

Version                   TNSLSNR for Linux: Version - Production

Start Date                18-NOV-2015 20:34:48

Uptime                    0 days 0 hr. 0 min. 0 sec

Trace Level               off

Security                  ON: Local OS Authentication

SNMP                      OFF

Listener Parameter File   /u01/app/oracle/product/11.2.0/xe/network/admin/listener.ora

Listener Log File         /u01/app/oracle/product/11.2.0/xe/network/log/diag/tnslsnr/localhost/listener/alert/log.xml

Listening Endpoints Summary...



Services Summary...

Service "PLSExtProc" has 1 instance(s).

  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...

The command completed successfully


[root@localhost ~]# su - oracle

Last login: Wed Nov 18 20:32:43 IST 2015 on pts/1

[oracle@localhost ~]$ . setDB.env

[oracle@localhost ~]$ sqlplus sys/sys@XE as sysdba

Connected to:

Oracle Database 11g Express Edition Release - 64bit Production




Continue to #seeITwithSanjay!

Saturday, September 19, 2015

Node Manager associated with machine is not reachable

The Node Manager associated with machine is not reachable!


Error: Following error is received while starting the managed servers from WLS console:

For server <server_name>, the Node Manager associated with machine <machine_name> is not reachable.






Cause: One of the reason you get this is error, is the incorrect properties set for nodemanager in “” file.


Detail RCA:

The Node Manager details can be configured from following location in WLS console:

Home > Environment > Machines > “You Machine” > Configuration > Node Manager > Type:


This is where most of the times people forget to change the value of listener type as “Plain” and use default type “ssl”, without configuring SSL.

In such cases when you start the nodemanager, it comes up without any complaints, and still you end up with domain that is unable to access nodemanager.


The devil lies in the details!

If you observe the nodemanager startup log, you’ll notice the below line, which indicates that listener has started in secure mode and not plain mode.

“<INFO> <Secure Socket listener started on port 5556, host />”



While some do remember to configure the node manager type as Plain in WLS console, they still face this issue, as one also needs to ensure that the SecureListener” parameter is set to false in “DOMAIN_HOME/ nodemanager/”.


So the final Solution is:

1.       Remember to change the Weblogic listener type parameter to

“Plain” in “Home > Environment > Machines > “You Machine” > Configuration > Node Manager > Type:”

2.       Ensure that “SecureListener” parameter is set to false in “DOMAIN_HOME/ nodemanager/”.