RSA1 Database error 12154 at CON issue

[tolulope_okusaga]

Good day,

I am trying to extract data from an Oracle database that is hosted on

another server.

I have configured the tnsnames.ora at the OS level.

I completed a test with tnsping and also connect to the database via

sqlplus. Everything works fine at the OS level.

I have created the connection parameters via tx:DBCO

However i get the system message with text "Database error 12154 at CON"when i create a DB connection via tx:RSA1.

Regards,

Tolu

[Former Member · Accepted solution]

Hi,

Just a confirmation.

Your test with tnsping and connect to the database via sqlplus is running on the app server?

Regards

Bill

[tolulope_okusaga · Accepted solution]

Hi Chie,

The SAP BW system is running on server 1.

Source database is running on server 2.

All the OS and sql test was completed on server 1.

All OS and sql test passed on server 1.

Regards,

Tolu

[former_member206552 · Accepted solution]

Hi Tolu,

is the connection test from DB02 successfull ?

Reason why I'm asking is because i have been at a client where the ORASID and SIDADM users use diffrent tnames.ora file like ORASID (/oracle/SID/11202/network/admin/tnsnames.ora) and SIDADM (/sapmnt/SID/profile/oracle/tnsnames.ora).

you can test from DB02 or you can use job (sa38) ADBC_TEST_CONNECTION to test the connection.

also in dbco Conn. Info only use the entried that was used to TNSPING (conenction name) with for instance SID.WORLD

Best Regards

Marius

[tolulope_okusaga · Accepted solution]

Hi Maruis,

The tnsnames in the directories are the same.

I tested the connection via program ADBC_TEST_CONNECTION and below is the result.

I tried connecting to create the DB using tx:db02 however the process failed.

I have an existing database on database connected on tx:db02 however if i try to connect to the same database using tx:rsa1 the process fails.

cloud you further explain your last paragraph

"also in dbco Conn. Info only use the entried that was used to TNSPING (conenction name) with for instance SID.WORLD"

On a different hand if you have created an ORACLE DB connect using tx: rsa1 kindly send me a screen shot of what the description of the connection tx:dbco.

regards,

Tolu

[former_member206552 · Accepted solution]

Morning Tolu,

First you create the TNSNAMES.ORA entry, in this case i create a new one called TST.WORLD

make sure you can TNSPING TST and its successful

Logon to SAP and create the entry in DBCO, for now i called mine just TST

The CONN. INFO must be the name of the new connection I called my TST.WORLD

go to SA38 and run ADBC_TEST_CONNECTION (this is to test the connection)

supply the DB Connectiom name used in DBCO to create the connection (TST)

and the final result connection working

If this does not work please supply the TNSNAMES.ORA entry along with the SQLNET.ORA entry

I check the RSA1 setting for external oracle databases and if you use the example above it will work, remember you need to supply the username (and password) for the schema owner you would like to access

Best Regards

Marius

[tolulope_okusaga · Accepted solution]

Excellent Maruis,

You rock!

The issue was the connection info. The SID.WORLD is the right parameter and not the SSID;DBOST

Regards,

Tolu

[former_member206552 · Accepted solution]

Hi Tolu,

Any time, glad I was able to assist

Best Regards

Marius

[Reagan]

Hello

Is it possible to provide the contents of the tnsnames.ora ?

Regards

RB

[former_member188080]

check below thread

Note 443867 - ORA-12154 Collective SAP note

http://scn.sap.com/thread/3194962

check last reply in above thread

http://scn.sap.com/thread/769294

Thanks and regards

Kiran

[Former Member]

Hi Tolulope,

oerr ora 12154

12154, 00000, "TNS:could not resolve the connect identifier specified"

// *Cause:  A connection to a database or other service was requested using

// a connect identifier, and the connect identifier specified could not

// be resolved into a connect descriptor using one of the naming methods

// configured. For example, if the type of connect identifier used was a

// net service name then the net service name could not be found in a

// naming method repository, or the repository could not be

// located or reached.

// *Action:

//   - If you are using local naming (TNSNAMES.ORA file):

//      - Make sure that "TNSNAMES" is listed as one of the values of the

//        NAMES.DIRECTORY_PATH parameter in the Oracle Net profile

//        (SQLNET.ORA)

//      - Verify that a TNSNAMES.ORA file exists and is in the proper

//        directory and is accessible.

//      - Check that the net service name used as the connect identifier

//        exists in the TNSNAMES.ORA file.

//      - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA

//        file.  Look for unmatched parentheses or stray characters. Errors

//        in a TNSNAMES.ORA file may make it unusable.

//   - If you are using directory naming:

//      - Verify that "LDAP" is listed as one of the values of the

//        NAMES.DIRETORY_PATH parameter in the Oracle Net profile

//        (SQLNET.ORA).

//      - Verify that the LDAP directory server is up and that it is

//        accessible.

//      - Verify that the net service name or database name used as the

//        connect identifier is configured in the directory.

//      - Verify that the default context being used is correct by

//        specifying a fully qualified net service name or a full LDAP DN

//        as the connect identifier

//   - If you are using easy connect naming:

//      - Verify that "EZCONNECT" is listed as one of the values of the

//        NAMES.DIRETORY_PATH parameter in the Oracle Net profile

//        (SQLNET.ORA).

//      - Make sure the host, port and service name specified

//        are correct.

//      - Try enclosing the connect identifier in quote marks.

//

//   See the Oracle Net Services Administrators Guide or the Oracle

//   operating system specific guide for more information on naming.

As per error above if you do not have access request correct entry for tnsnames.ora to be maintained by your basis team or Oracle DBA.

Kind Regards,

Johan

[ranganath_korata]

Hi,

It would be a task of the Basis, so please have them take a look at it.

Thanks,

Ranga