Sie sind auf Seite 1von 5

Getting Started Newsletters Store

Products Services & Support About SCN Downloads


Industries Training & Education Partnership Developer Center
Lines of Business University Alliances Events & Webinars Innovation
Login Register Welcome, Guest
Activity Communications Actions
Browse
Mohsin M Nov 7, 2010 7:09 PM
0
Tweet
9 Replies Latest reply: Apr 23, 2013 7:57 PM by Richard Howard
SAP down - ERROR => CONNECT failed with
sql error 12514
This question is Assumed Answered.
Hello All,
After restart SAP not getting up.



R3trans log >>>

4 ETW000 [developertra,00000] Try to connect with default password 13 0.033705
4 ETW000 [developertra,00000] Connecting as SAPR3/<pwd>@SID on connection 0 ... (dbsl 46D
220209)
4 ETW000 20 0.033725
4 ETW000 [developertra,00000] -->oci_logon(con_hdl=0, user='SAPR3', dbname='SID')
4 ETW000 20 0.033745
*4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'olog' failed: rc = 12514 931 0.034676*
*4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error 12514*4
ETW000 27 0.034703
4 ETW000 [dblink ,00627] ***LOG BY2=>sql error 12514 performing CON 142 0.034845
4 ETW000 [dblink ,00627] ***LOG BY0=> 15 0.034860
2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'SID'"
hostname:sidam 53>

*********************************************************************************************
listener.log

TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
07-NOV-2010 19:05:23 * (CONNECT_DATA=(SERVER=DEDICATED)
(SERVICE_NAME=SID.WORLD)(CID=(PROGRAM=R3trans)(HOST=hostname)(USER=SIDadm))) *
(ADDRESS=(PROTOCOL=tcp)(HOST=144.119.161.17)(PORT=60626)) * establish * SID.WORLD *
12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor


lsnrctl >>

Services Summary...
Service "sid" has 1 instance(s).
Instance "sid", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
LSNRCTL>

*********************************************************************************************


SQL> select status from v$instance;

STATUS
-
OPEN

but SAP is not getting up.

*********************************************************************************************

hostname:orasid 41> more listener.ora

Page 1 of 5 SAP down - ERROR => CONNECT failed wit... | SCN
10/ 6/ 2013 https://scn.sap.com/thread/1824310
################
1. Filename......: listener.ora
2. Created.......: created by SAP AG, R/3 Rel. >= 4.0A
3. Name..........:
4. Date..........:
################
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL=IPC)
(KEY= sid.WORLD)
)
(ADDRESS=
(PROTOCOL=IPC)
(KEY= sid)
)
(ADDRESS =
(COMMUNITY = SAP.WORLD)
(PROTOCOL = TCP)
(HOST = hostname)
(PORT = 1535)
)
)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SDU = 32768)
(SID_NAME = sid)
(ORACLE_HOME = /oracle/sid/102_64)
)
)
hostname:orasid 42>

*********************************************************************************************



hostname:orasid 43> more tnsnames.ora
1. tnsnames.ora Network Configuration File: /oracle/sid/102_64/network/admin/tnsnames.ora
2. Generated by Oracle configuration tools.

################
1. Filename......: tnsnames.ora
2. Created.......: created by SAP AG, R/3 Rel. >= 4.0A
3. Name..........:
4. Date..........:
################

LISTENER_sid.WORLD =
(ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = hostname)(PORT =
1535))


sid.WORLD =
(DESCRIPTION =
(ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = hostname)(PORT =
1535))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = sid.WORLD)
)
)

hostname:orasid 44>

***************************************************

listener.log

TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
07-NOV-2010 19:05:23 * (CONNECT_DATA=(SERVER=DEDICATED)
(SERVICE_NAME=SID.WORLD)(CID=(PROGRAM=R3trans)(HOST=hostname)(USER=SIDadm))) *
(ADDRESS=(PROTOCOL=tcp)(HOST=144.119.161.17)(PORT=60626)) * establish * SID.WORLD *
12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
Page 2 of 5 SAP down - ERROR => CONNECT failed wit... | SCN
10/ 6/ 2013 https://scn.sap.com/thread/1824310
Volker Borowski Nov 8, 2010 10:27 AM (in response to Gagan Deep Kaushal)
2671 Views
Average User Rating
(0 ratings)

Edited by: mohsinbasis on Nov 7, 2010 7:06 PM

Edited by: mohsinbasis on Nov 7, 2010 7:08 PM
Re: SAP down - ERROR => CONNECT failed with sql error 12514
Hello,

The 12514 error code means that it was possible to reach the listener
but that the listener had to reject the connection because he does not
know where to route the request

Please check note
563574 Composite SAP note ORA-12514

regards,
John Feely
Like (0)
John Feely Nov 7, 2010 11:03 PM (in response to Mohsin M)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
Hi,

The listener seem to be trying to connect to port 60626, however this port is not configured in your
listener.ora file. Please check any listener file available in <dir_profile>/oracle directory and correct
the listener details in it. Restart the listener for any changes done.
Like (0)
Atul Jawalkar Nov 7, 2010 11:29 PM (in response to John Feely)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
Hi,

It seems wrong Listener config , review once.

what is the ouput of

TNSPING SID

Regards,
Like (0)
Gagan Deep Kaushal Nov 8, 2010 5:46 AM (in response to Mohsin M)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
Hi,

all your "sid" in your config files are lowercase, while
R3trans tries to connect with uppercase "SID".
This could be a missmatch.

Check "sidadm" Environment for TNS_ADMIN. If set, i.e. to
/sapmnt/SID/profile/oracle
check sqlnet.ora and tnsnames.ora at that position.

Volker
Page 3 of 5 SAP down - ERROR => CONNECT failed wit... | SCN
10/ 6/ 2013 https://scn.sap.com/thread/1824310
mohsin m Nov 10, 2010 4:56 PM (in response to Konstantina Stamelou)
Like (0)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
Hi ,

Please check service_name parameter of your database.

Also check listener.log

Abhijit

Edited by: Abhijeet Siras on Nov 8, 2010 4:14 PM
Like (0)
Abhijeet Siras Nov 8, 2010 11:44 AM (in response to Mohsin M)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
listener.log

TNS-12514: TNS:listener does not currently know of service requested in connect
descriptor
07-NOV-2010 19:05:23 * (CONNECT_DATA=(SERVER=DEDICATED)
(SERVICE_NAME=SID.WORLD)(CID=(PROGRAM=R3trans)(HOST=hostname)
(USER=SIDadm))) * (ADDRESS=(PROTOCOL=tcp)(HOST=144.119.161.17)
(PORT=60626)) * establish * SID.WORLD * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect
descriptor


lsnrctl >>



(HOST = hostname)
(PORT = 1535)


Hi,

even if the correct IP of "hostname" is 144.119.161.17, it is obvious from listener.log that the listener is
trying to establish a connection at port 60626 and not at port 1535.
Please check your configuration again.
Are there more than one system running on the same server?

Regards,
Constantina
Like (0)
Konstantina Stamelou Nov 10, 2010 1:27 PM (in response to Mohsin M)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
hostname:oraSID 5> more tnsnames.ora
1. tnsnames.ora Network Configuration File: /oracle/SID/102_64/network/admin/tnsnames.ora
2. Generated by Oracle configuration tools.

################
1. Filename......: tnsnames.ora
2. Created.......: created by SAP AG, R/3 Rel. >= 4.0A
3. Name..........:
4. Date..........:
################
SID.WORLD=
Page 4 of 5 SAP down - ERROR => CONNECT failed wit... | SCN
10/ 6/ 2013 https://scn.sap.com/thread/1824310
Follow SCN
Site Index Contact Us SAP Help Portal
Privacy Terms of Use Legal Disclosure Copyright
0
Tweet
(DESCRIPTION =
(SDU = 32768)
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = SID.WORLD)
(PROTOCOL = TCP)
(HOST = hostname)
(PORT = 1535)
)
)
(CONNECT_DATA =
(SID = SID)
(GLOBAL_NAME = SID.WORLD)
)
)
hostname:oraSID 6>



Now issue is resolved
Like (0)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
tnx
Like (0)
Mohsin M Nov 23, 2010 7:19 AM (in response to Mohsin M)
Re: SAP down - ERROR => CONNECT failed with sql error 12514
I just used this Thread to resolve the same/similar problem, so I'll add some additional info.

We patched to 11.2.0.3 and started getting some ORA-12514 errors. When I ran "lsnrctl status"
the SID.WORLD service was no longer displaying in a READY state. Why? The listener.ora and
tnsnames.ora had not changed.

TNSPING was ok
R3trans -x was ok
11.2.0.3 /oracle/client checked out fine
I could actually do a successful "startsap" and run ok

The issued turned out to be that LOCAL_LISTENER parameter in the initSID.ora was blank. If
your tnsnames.ora file has a "LISTENER_SID.WORLD" entry, this parameter needs to match it. I
updated the parameter with the following:

ALTER SYSTEM SET LOCAL_LISTENER='LISTENER_SID';

Immediately after setting it, the "lsnrctl status" was now showing the SID.WORLD service.

I do not know if the 11.2.0.3 Patchset or the SBP had anything to do with blanking out this
parameter but I have to assume that it did since the SID.WORLD service was fine before we
begain.

Thanks to John Feely. The note he referenced above led me down this path.
Like (1)
Richard Howard Apr 23, 2013 7:57 PM (in response to Mohsin M)
Page 5 of 5 SAP down - ERROR => CONNECT failed wit... | SCN
10/ 6/ 2013 https://scn.sap.com/thread/1824310