DBCON/DBACOCKPIT Connection to External Oracle Database

[former_member209924]

Dear Experts,

We are troubleshooting a database connection in DBCON/DBACOCKPIT to our external Oracle database.  We have the external database connection working in our Solution Manager system, but cannot get the ERP systemto talk to the external database.  Details below.

We are able to connect to the remote database with SQLPlus from the ERP system with the following command, but going through SAP results in 12154 Error.

S:\usr\sap\oracle>sqlplus.exe /nolog

SQL*Plus: Release 10.2.0.2.0 - Production on Fri May 4 22:30:31 2012

Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.

SQL> conn ITA/xxx@ITAPREFN

Connected.

SQL> exit

Our Solman System is ALL SET, everything worked on the first try.  ERP system is causing all the headache.

System Information:

OS - Windows Server 2003 64bit

ERP - ERP 600/NW 700 with SP18

Kernel - 700 64bit UC with latest patch

OS - Windows Server 2008 R2

Solman - Solman 7.1 with SP08

Kernel - 720 64bit UC with Patch 90

OS - Windows Server 2003 64bit

Remote Oracle Database - Oracle9i Enterprise Edition Release 9.2.0.1.0

Our Setup in ERP and Solman Systems.  Both setups are exactly identical.

Database Library Files

ORA library files (specific to SAP Kernel) were downloaded or moved to:

S:\usr\sap\TSE\DVEBMGS63\exe

S:\usr\sap\PSM\DVEBMGS00\exe

User Environment Variables

CLIENT_ORACLE_HOME set to S:\usr\sap\oracle

TNS_ADMIN set to S:\usr\sap\TSE\SYS\profile\oracle

Instance Profile Parameter

DIR_CLIENT_ORAHOME set to S:\usr\sap\oracle

Oracle Directories and Files

Oracle Client Version - 10.2.0.2.0

sqlnet.ora

NAMES.DIRECTORY_PATH = (EZCONNECT,TNSNAMES)

tnsnames.ora

ITAPREFN=

(DESCRIPTION =

   (ADDRESS_LIST =

     (ADDRESS =

      (COMMUNITY = SAP.WORLD)

       (PROTOCOL = TCP)

      (HOST = x.x.x.x)

      (PORT = 1521)

     )

   )

   (CONNECT_DATA =

     (SID = ITAPREFN)

     (GLOBAL_NAME=ITAPREFN.WORLD)

)

)

protocol.ora

empty file

DBCON Settings

Connection Test from (SE38 / ADBC_TEST_CONNECTION) and Logs

dev_w1 log of ERP System

B Fri May 04 21:08:13 2012

B  Connect to ITA as ITA with ITAPREFN

C  Application info callback registered.

C  Client NLS setting (by OCINlsGetInfo): con=1, 'AMERICAN_AMERICA.UTF16'

C  Connecting as ITA/<pwd>@ITAPREFN on connection 1 (nls 0) ... (dbsl 700 110412, UNICODE[2])

C  Attaching to DB Server ITAPREFN (con=1,svchp=000000003006BDF8,srvhp=00000000322BD2A8)

C 

C Fri May 04 21:08:22 2012

C     OCIServerAttach(OCI_DEFAULT) failed with SQL error 12154:

C     ORA-12154: TNS:could not resolve the connect identifier specified                                                        

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

[dbsloci.c    11306]

B  ***LOG BY2=> sql error 12154      performing CON        [dbds#2 @ 1056] [dbds    1056 ]

B  ***LOG BY0=> con=1(ITAPREFN): ORA-12154: TNS:could not resolve the connect identifier specified [dbds#2 @ 1056] [dbds    1056 ]

B  ***LOG BY1=> sql error 12154      [dbacds#2 @ 1433] [dbacds  1433 ]

B 

B Fri May 04 21:24:10 2012

B  Connect to ITA as ITA with ITAPREFN

C  Application info callback registered.

C  Client NLS setting (by OCINlsGetInfo): con=1, 'AMERICAN_AMERICA.UTF16'

C  Connecting as ITA/<pwd>@ITAPREFN on connection 1 (nls 0) ... (dbsl 700 110412, UNICODE[2])

C  Attaching to DB Server ITAPREFN (con=1,svchp=000000003006BCB8,srvhp=000000003232BB08)

C 

C Fri May 04 21:24:19 2012

C     OCIServerAttach(OCI_DEFAULT) failed with SQL error 12154:

C     ORA-12154: TNS:could not resolve the connect identifier specified                                                        

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

[dbsloci.c    11306]

B  ***LOG BY2=> sql error 12154      performing CON        [dbds#2 @ 1056] [dbds    1056 ]

B  ***LOG BY0=> con=1(ITAPREFN): ORA-12154: TNS:could not resolve the connect identifier specified [dbds#2 @ 1056] [dbds    1056 ]

B  ***LOG BY1=> sql error 12154      [dbacds#2 @ 1433] [dbacds  1433 ]

A 

A Fri May 04 21:47:34 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

A 

A Fri May 04 21:49:11 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

A 

A Fri May 04 21:49:57 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

A 

A Fri May 04 21:50:40 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

A 

A Fri May 04 21:50:53 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

A 

A Fri May 04 21:51:29 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

A 

A Fri May 04 21:52:49 2012

A  *GENER* starting remote generation: AL01610R (requested by W1).

B 

B Fri May 04 22:22:53 2012

B  Connect to ITA as ITA with ITAPREFN

C  Application info callback registered.

C  Client NLS setting (by OCINlsGetInfo): con=1, 'AMERICAN_AMERICA.UTF16'

C  Connecting as ITA/<pwd>@ITAPREFN on connection 1 (nls 0) ... (dbsl 700 110412, UNICODE[2])

C  Attaching to DB Server ITAPREFN (con=1,svchp=000000003006BB78,srvhp=00000000321DD448)

C 

C Fri May 04 22:23:02 2012

C     OCIServerAttach(OCI_DEFAULT) failed with SQL error 12154:

C     ORA-12154: TNS:could not resolve the connect identifier specified                                                        

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

[dbsloci.c    11306]

B  ***LOG BY2=> sql error 12154      performing CON        [dbds#2 @ 1056] [dbds    1056 ]

B  ***LOG BY0=> con=1(ITAPREFN): ORA-12154: TNS:could not resolve the connect identifier specified [dbds#2 @ 1056] [dbds    1056 ]

B  ***LOG BY1=> sql error 12154      [dbacds#2 @ 1433] [dbacds  1433 ]

Any help would be much appreciated.

Regards,

Ravi

[former_member209924 · Accepted solution]

Thank you all for your suggestions.

We have upgraded our ERP System to EHP5 and DB Connection now works with new version of SAP/Kernel.

Ravi

[Former Member]

Hi Experts,

need help in the similar issue mentioned above. where i am trying to configure Non SAP Databse into solution manager for database monitoring purpose. Getting error in Managed System Configuration in 2nd step Enter system parameter after entering the user id SA and password ..

Error " DBA Cockpit connection couldnot be established"

Thanks in advance..

[ashish_vikas]

you should open a new discussion, generally ppl do not open question marked as answered.

best regards

ashish

[Former Member]

Hi Ravi,

Have you ever checked the note, below?

Note 443867 - ORA-12154 Collective SAP note

Best regards,

Orkun Gedik

[former_member209924]

Hi Orkun,

Thanks for the reply.

Yes, this is THE note we used to troubleshoot this issue.  We have everything setup as mentioned in the note, this is how we got the Solman system working.  The ERP system is the only one that is not working.

As you can see from my first post, the Kernel is lot different on both systems.  But, again this is really puzzling to me, because I've set this connection up before on 640 Kernels.

Not matter how many times we troubleshoot, we always end up with "ORA-12154: TNS:could not resolve the connect identifier specified "

We also have an OSS message open with SAP, so far the only solution they have come up with is Kernel upgrade.

Regards,

Ravi

[nicholas_chang]

Hi,

Perhaps you can try to update the dbsl (db librabry) to the latest and see how it goes.

Cheers,

Nicholas Chang

[former_member182307]

Hello,

Have you copied the TNSNAMES.ORA file from your database/network/admin directory, in which you have set the TNS connection information to ITA, to S:\usr\sap\TSE\SYS\profile\oracle ?

The SAP workprocesse use the tnenames.ora in the directory identified by the TNS_ADMIN variable and not the one in the "database/network/admin" .

Best regards,

Steve.

[former_member209924]

Steve,

Thanks for the reply.

Yes, I did move all ORA files over to S:\usr\sap\TSE\SYS\profile\oracle. All Environment Variables set and pointing to this location.  This is the same setup we have in Solman system, I just do not understand why this would work on one system and not others.

Furthermore, I've checked with our Network/Firewall team and double checked the rules.  There are no rules blocking traffic to the remote database.

Regards,

Ravi