I am getting the following errors while from the lsnrctl status
command:
C:\\Users\\pna105>lsnrctl stat
LSNRCTL for 64-bit Windows: Version 11.
In my case somehow windows listener service had stopped working so I was not able to connect to Qracle using SQL Developer. However I was able to connect through sqlplus
.
Below solution worked for me:
First, ensure that your listener service is running.
C:\Documents and Settings\ME>lsnrctl status
If the listener service is not running, re-start the listener service using the Windows task manager or use the DOS command line utility to re-start the Windows service with the net start
command:
C:\Documents and Settings\ME>net start OracleOraDb10g_home1TNSListener
Try to start the listener service using lsnrctl
from DOS prompt.
lsnrctl start
I managed to resolve the issue that caused the configuration to fail on a docker container running the Hortonworks HDP 2.6 Sandbox.
If the initial configuration fails the listener will be running and will have to be killed first:
ps -aux | grep tnslsnr
kill {process id identified above}
Then next step is then to fix the shared memory issue which makes the configuration process fail.
Oracle XE requires 1 Gb of shared memory and fails otherwise (I didn't try 512 mb) according to https://blogs.oracle.com/oraclewebcentersuite/implement-oracle-database-xe-as-docker-containers.
vi /etc/fstab
change/add the line to:
tmpfs /dev/shm tmpfs defaults,size=1024m 0 0
Then reload the configuration by:
mount -a
Keep in mind that the next time you restart the docker container you might have to do 'mount -a'.
In my case, I tried to start the listener via console:
> lsnrctl star
This command printed the following error:
TNS-12560: TNS:protocol adapter error
TNS-00583: Valid node checking: unable to parse configuration parameters
So, I performed the following actions:
listener.ora
or sqlnet.ora
file contains special characterslistener.ora
or sqlnet.ora` file are in wrong format or syntaxlistener.ora
or sqlnet.ora
file have some left justified parenthesis which are not accepted by oracle parser.Have a look at these files and check the proper syntax. If possible remove/rename sqlnet.ora and try to restart the listener. Or remove/rename both listener.ora or sqlnet.ora file and recreate it properly. These will defenitely resolve the issue.
I had the same problem. Solution in my case: run CMD as ADMINISTRATOR. then type and execute: "lsnrctl start" wait about 2 minutes then should work. (in my case was only 50 seconds, but just to be on the safe side)
I encounter similar problem when installing oracle 11gR2 on Windows 2012 server. the problem is solved when I run cmd.exe as Admistrator privilege and run "lsnrctl start LISTENER".
Check that ORACLE_HOME environment variable is pointing to the correct oracle home. In my case it was changed by another software installation.