cancel
Showing results for 
Search instead for 
Did you mean: 

Hello Experts Please help me to solve this problem.

Former Member
0 Kudos

Hello Experts,

I am getting a problem while installing the SOLUTION MANAGER 4.0.

in step 17/45 IMPORT ABAP :

the problem is :

ERROR 2008-04-29 03:10:28.110

CJS-30023 Process call '/usr/sap/SLM/SYS/exe/run/R3load -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.

when i saw R3load.exe.log file it has the following contain :

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

/usr/sap/SLM/SYS/exe/run/R3load: START OF LOG: 20080428095833

/usr/sap/SLM/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP

/usr/sap/SLM/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]

Compiled Jul 14 2007 02:19:03

/usr/sap/SLM/SYS/exe/run/R3load -testconnect

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12505

DbSl Trace: CONNECT failed with sql error '12505'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12505

DbSl Trace: CONNECT failed with sql error '12505'

(DB) ERROR: db_connect rc = 256

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12505

DbSl Trace: CONNECT failed with sql error '12505'

DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12505

DbSl Trace: CONNECT failed with sql error '12505'

(DB) ERROR: DbSlErrorMsg rc = 99

/usr/sap/SLM/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/SLM/SYS/exe/run/R3load: END OF LOG: 20080428095834

Please can any body help me to solve this problem.

waiting for fast response, as my installtion is pending due to this problem.

have a nice day.

Regards,

Shivendra.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

I know the question has been asked 2 years ago.

But, I'm going to answer for the ones who will need an issue, and will look for a solution.

If you use the wrong port, you have to change 3 files and no only 2 :

oracle/SID/102_64/network/admin/listener.ora

/oracle/SID/102_64/network/admin/tnsnames.ora

/sapmnt/SID/profile/oracle/tnsnames.ora

Former Member
0 Kudos

Xavier,

I'd say: It depends.

The third file you mentioned has to be changed only in case it really exists.

On all of our SAP systems I can only see the two other.

And somehow SAP is up and running anyway...

markus_doehr2
Active Contributor
0 Kudos

Did you install the database when it's been requested by sapinst or before the installation? If you did install Oracle before then your configuration is incomplete.

Markus

Former Member
0 Kudos

Hello Markus,

I installed my oracle database only when sapinst asked me to install the database.

markus_doehr2
Active Contributor
0 Kudos

This is really strange. I did a lot of installation and I never ran into that problem.

Do you have a tnsnames.ora?

Markus

Former Member
0 Kudos

Hi!

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor.

Check the parameters for connect to the database.

The correct SID and port you can find in:

Under OS user oraSAPSID execute the command - lsnrctl status

Former Member
0 Kudos

Hi Alexey!

Thanks for your valuable Answer, but still i am getting the same problem.

I think that my Listener is started but it is lont listening.

it is refusing connection from SAP to Database.

Please let me know if you have any ans.

in this server i already had one oracle server so i changed the name of LISTENER to LISTENER_SLM in listener.ora and also changed the port no 1527 to 1528.

and changed the same port no in tnsname.ora.

please help me out if you have any idea.

waiting for your response.

former_member227600
Contributor
0 Kudos

Hi,

Follow the following SNOTE

[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=576919]

the above note will resolve your problem

Karan

Former Member
0 Kudos

Hi,

The following should be verified:

(1) check what DB instances the listener currently is aware of. This can be done with the command 'lsnrctl services'.

(in case you listener does not have the default name LISTENER, then use 'lsnrctl services <listener name>' )

(2) Perhaps there is an issue with the dynamic instance registration, even though the error code is different, you should nevertheless check the points from note #563574.

(3) Verfiy the value of the parameter local_listener (see mentioned note). Since you have changed the listener, the parameter might still be wrong.

In case local_listener is correcly set you should give the command

ALTER SYSTEM REGISTER;

a try.

Best Regards,

Michael

Former Member
0 Kudos

Hi Every body!

I have resolved this problem.

i re- installed The system with new Listener Name and Port no.

at the time of Parameter defination and i have installed it successfully.

thanks to all of you.

for your nice suggestion and help.