You can ignore that error. Try to stop & start the listener again. You shouldn't see the error this time.Originally Posted by varaprasad_1261
The error is usually due to the Windows listener service not be created for the newDB listener the very first time you start the newDB listener.Code:lsnrctl stop newDB lsnrctl start newDB