cancel
Showing results for 
Search instead for 
Did you mean: 

ERROR => OCI-call 'OCIServerAttach' failed: rc = 12154

0 Kudos

Hi,</br>

</br>

Our QAS system is DRQ.</br>

Our PRD system is DRP.</br>

</br>

External non-sap oracle DB is MENP, MEBP, MEPP, MEDP.</br>

</br>

MENP, MEBP, MEPP is registed the past.</br>

MEDP is registered newly.</br>

</br>

DRQ and DRP is registered "tnsnames.ora" file and TA DBCO with same

information.</br>

</br>

In DRQ,</br>

"tnsping MENP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

"tnsping MEBP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

"tnsping MEPP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

"tnsping MEDP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

</br>

In DRP,</br>

"tnsping MENP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

"tnsping MEBP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

"tnsping MEPP" is OK and "ADBC_TEST_CONNECTION" program is OK.</br>

"tnsping MEDP" is OK and "ADBC_TEST_CONNECTION" program is ERROR.</br>

</br>

It's same "tnsnaems.ora" file information of DRQ and DRP.</br>

I'm check up again and again.</br>

</br>

Despite the same information, DRP appear ERROR.</br>

</br>

In DRQ and DRP,</br>

sqlnet.ora, listener.ora, tnsnames.ora file is all same.</br>

</br>

I draw a comparison between DRQ and DRP.</br>

I check up again and again.</br>

</br>

</br>

-


Trace Data dev_w3 of DRP----


</br>

B Wed Oct 7 10:12:31 2009</br>

B Connect to MEDP as m60user with MEDP</br>

C got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment</br>

C Client NLS settings:</br>

C Connecting as m60user/<pwd>@MEDP on connection 1 (nls_hdl 0) ...</br>

(dbsl 640 070208)</br>

C Nls CharacterSet NationalCharSet C</br>

EnvHp ErrHp ErrHpBatch</br>

C 0 UTF8 1</br>

0x6000000003c16650 0x6000000003c29108 0x6000000003c28b18</br>

C Attaching to DB Server MEDP</br>

(con_hdl=1,svchp=0x60000000052c0d80,srvhp=0x60000000064884b8)</br>

C *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12154</br>

[dboci.c 4289]</br>

C *** ERROR => CONNECT failed with sql error '12154'</br>

[dbsloci.c 11410]</br>

B ***LOG BY2=> sql error 12154 performing CON [dbds#3 @</br>

1044] [dbds 1044 ]</br>

B ***LOG BY0=> ORA-12154: TNS:could not resolve service name [dbds#3 @</br>

1044] [dbds 1044 ]</br>

B ***LOG BY1=> sql error 12154 [dbacds#2 @ 1317] [dbacds 1317 ]</br>

-


</br>

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Have a look at SAP note 443867 - its focus is exactly on the oracle connection error you mentioned.

Something seems to be wrong with your tnsnames.ora or sqlnet.ora. Can you provide its content?

Also please check that none of the lines used within those two files for the connection definition have a line feed. It might seem that the line is complete but actually oracle cannot use it due to the line feed.

0 Kudos

It's same sqlent.ora, tnsnames.ora file contents of DRQ and DRP.

sqlnet.ora, tnsnames.ora of DRQ ->

/oracle/DRQ/920_64/network/admin

sqlnet.ora, tnsnames.ora of DRP ->

/oracle/DRP/920_64/network/admin

-


sqlnet.ora----


################

  1. Filename......: sqlnet.ora

  2. Created.......: created by SAP AG, R/3 Rel. >= 6.10

  3. Name..........:

  4. Date..........:

  5. @(#) $Id: //bc/640-2/src/ins/SAPINST/impl/tpls/ora/ind/SQLNET.ORA#4 $

################

AUTOMATIC_IPC = ON

TRACE_LEVEL_CLIENT = OFF

NAMES.DEFAULT_DOMAIN = WORLD

NAME.DEFAULT_ZONE = WORLD

SQLNET.EXPIRE_TIME = 0

TCP.NODELAY=YES

-


-


tnsnames.ora----


MEDP.WORLD =

(DESCRIPTION =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP)(HOST = 10.xx.xx.xx)(PORT = 2006))

(ADDRESS = (PROTOCOL = TCP)(HOST = 10.xx.xx.xx)(PORT = 2006))

)

(CONNECT_DATA =

(SERVICE_NAME = MEDP)

(SERVER = DEDICATED)

)

)

-


Former Member
0 Kudos

Aint there one line

(ADDRESS = (PROTOCOL = TCP)(HOST = 10.xx.xx.xx)(PORT = 2006))

too much in your config?

0 Kudos

I solved problem.

In DRP, cosist of 3 instance.

In tnsnames.ora file of application server instance, add the tns contents.

Thanks

Former Member
0 Kudos

Great - in that case please mark this thread as answered.