cancel
Showing results for 
Search instead for 
Did you mean: 

TNS-12541: TNS: no listener when execute startdb

Former Member
0 Kudos

Dear,

i have install a nw04s System ABAP + J2EE and try to start

the db with startdb. I got this error:

Used TNSNAMES adapter to resolve the alias

Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD) (PROTOCOL = TCP) (HOST = kratie) (PORT = 1527))) (CONNECT_DATA = (SID = SOT) (GLOBAL_NAME = SOT.WORLD)))

TNS-12541: TNS:no listener

V2 connect is not available. Terminating

/usr/sap/SOT/SYS/exe/run/startdb: Terminating with error code 14

I could start the listner with the oracle user manually

and afterward start the stardb or startsap. When i first

start the listener that way then it is possible to start

startsap or stardb with no problem. But why do i have

to start the listener by hand?

best regards,

Ly-Na Phu

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Make the start-options of TNSlistner as automatic from manual, so that when you boot your system it gets started and you will not face the problem.(In services right-click on the component and set the status from manual to automatic). Hope the answer is usefull.

Regards:-

<b>Santosh.D</b>

Former Member
0 Kudos

Hi Santosh,

thanks for your answer. I have'n told you that my nw04

is running under linux. So it is a different way how

to make the listener run as service.

regards,

Ly-Na Phu

Former Member
0 Kudos

You can automate the process of starting the listener if you use windows server.

If it's unix you have to start it manually.this is a standard practice.

If you use startsap or startdb it will check for the listener process,so you are getting the error.

Any way you can start your DB seperately at DB level and start SAP using startsap R3 and everything will be up but you can not work because DB can not accept any client requests as the listener is not running.

Former Member
0 Kudos

Hi Naidu,

thanks for you answer. Now i understand that the listener

ist not configured by sapinst automatically and that one

have to start it manually. At windows sapinst do that and

the listener ist comming automatically when booting.

At linux it has to be put in the startup procedure e.g.

in the runlevel 3 rc3.d. If not doing so we have to start

the listener manually. But everything else work fine.

Thanks,

Ly-Na Phu