DbSl Trace: CONNECT failed with sql error 12154.

[carlos_zhang3]

Dear support ,

I am going to export the SAPR3 4.7 x 200 (unicode version) by MASTER installation tools .

When executing the R3ldctl ....

It stopped and show me :

ERROR 2010-04-09 19:07:41

MOS-01012 PROBLEM: 'F:\usr\sap\D19\SYS\exe\run/R3ldctl.exe -l ./R3ldctlExport.log -p G:\EXPORTD19/DATA/ ' returned with '2' which is not a defined as a success code.

And i checked the log from sapinst directory :

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154

DbSl Trace: CONNECT failed with sql error 12154.

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154

DbSl Trace: CONNECT failed with sql error 12154.

ERROR: DbSlConnect rc= 99

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154

DbSl Trace: CONNECT failed with sql error 12154.

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154

DbSl Trace: CONNECT failed with sql error 12154.

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154

DbSl Trace: CONNECT failed with sql error 12154.

DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12154

DbSl Trace: CONNECT failed with sql error 12154.

Does someone can help me fix this problem ? thank you .

Best regards,

Carlos Zhang

[stefan_koehler · Accepted solution]

Hello Carlos,

ORA-12154:	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.

You have set a connection identifier, that could not be resolved through tnsnames.ora file.

This can have two different reasons:

1) No or wrong entry tnsnames.ora (environment variable TNS_ADMIN or default location ORACLE_HOME/network/admin)

2) Wrong connect identifier is specified in environment or SAP profile (i am not quite sure how SAP resolves the connect identifier on windows), but normally the identifier is written to the file R3ldctlExport.log, so you can crosscheck this.

If you got the identifier just execute a "tnsping <IDENTIFIER>" and check which tnsnames.ora is used and its content.

Regards

Stefan

[carlos_zhang3]

Hi Rajesh ,

I have checked the oracle , it is up .

And everything is okay ...

Is the kernel version problem ?

[carlos_zhang3]

In addition , we are using 32bit windows 2003 r2 version OS with oracle 9i .

[Former Member]

Hi,

Is Oracle up ?

Mark

[Former Member]

Hi,

Please check if the LISTENER Service is running and database is also UP...

To check listener service :

Start --> Administrative Tools --> Services (For Windows)

(make the startup mode "Automatic")

For UNIX:

1. Open Terminal

2. # su - ora<sid>

3. # lsnrctl status (Use start and stop option to start/stop listener)

To check database is up:

Open command prompt and type the below commands.

sqlplus / as sysdba

SQL>select instance_name,status from v$instance;

Also check that you have defined below environment variables:

ORACLE_HOME

ORACLE_SID

and added path of $ORACLE_HOME\bin in your PATH variable

Then retry installation....

Regards.

Rajesh Narkhede