cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot start SAP using commond startsap on unix

Former Member
0 Kudos

Hi

I am facing issue while starting SAP , when i run Startsap command on Unix i am receiving following error.

-


saposcol already running

Running /usr/sap/CID/SYS/exe/run/startdb

Trying to start CID database ...

Log file: /home/cidadm/startdb.log

No SQL*Net V2 connect to CID available.

Check that the listener is running: "lsnrctl status".

Start the listener as user oracid: "lsnrctl start".

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

-


I have started listener lsnrctl by becoming system admin and lsnrctl is started still i am gettig above error

-


LSNRCTL> status

Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))

STATUS of the LISTENER

-


Alias LISTENER

Version TNSLSNR for Solaris: Version 10.2.0.2.0 - Production

Start Date 30-JUN-2010 07:51:50

Uptime 0 days 1 hr. 1 min. 30 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File /oracle/CID/102_64/network/admin/listener.ora

Listener Log File /oracle/CID/102_64/network/log/listener.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nsu1u660)(PORT=1521)))

The listener supports no services

The command completed successfully

-


Please let is know what is the issue.

Thanks

Uttam Borsare

Accepted Solutions (0)

Answers (2)

Answers (2)

markus_doehr2
Active Contributor
0 Kudos

> Listening Endpoints Summary...

> (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=nsu1u660)(PORT=1521)))

> The listener supports no services

Your listener.ora is not correct, the instance name is missing.

Markus

Former Member
0 Kudos

Hi

Thanks for ur reply but the sap application and database was running fine till few days back and no setting has been changed any

where.

Thanks

Uttam

markus_doehr2
Active Contributor
0 Kudos

> Thanks for ur reply but the sap application and database was running fine till few days back and no setting has been changed any

> where.

Without looking at the system it's impossible to give a reason. Make sure you start the listener with ora<SID>. If that doesn't help open an OSS call (BC-DB-ORA) and let the support have a look on the system.

Markus

Former Member
0 Kudos

Can you perform R3trans -d as sidadm user and post the output (if you get an error).

Kind regards,

Mark