Oracle Listener error in Import ABAP phase?

[Former Member]

I am installing PI7.1 on a host which has Solman 7.0 installed.

In the ABAP Import phase I get an error "Could not connect to database"

I see that the database and listener are running for PI. But sapinst is using the Solman listener for connecting to the database...which is currently stopped. I tried manually starting the solman listener but it starts and immediately stops.

Can someone tell me how to set the PI listener ? The listener status is mentioned below. The R3Load.exe log file is mentioned below that. The sapinst.log is mentioned in the end.

Would appreciate if someone could provide inputs.

Thanks

-

---

Listener Status
LSNRCTL> status
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SM1.WORLD))
STATUS of the LISTENER
-
Alias                     LISTENER
Version                   TNSLSNR for 64-bit Windows: Version 10.2.0.4.0
ction
Start Date                21-JAN-2009 14:47:26
Uptime                    0 days 0 hr. 42 min. 43 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   C:\oracle\SM1\102\network\admin\listener.ora
Listener Log File         C:\oracle\SM1\102\network\log\listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\SM1.WORLDipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=
.\pipe\SM1ipc)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=host123)(PORT=1527)))
Services Summary...
Service "SM1" has 1 instance(s).
  Instance "SM1", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully 

R3Load.exe log
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20090121153010
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/710_REL/src/R3ld/R3load/R3ldmain.c#10 $ SAP
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Oct 26 2007 00:59:33
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect 
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12505
DbSl Trace: CONNECT failed with sql error '12505'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12505
DbSl Trace: CONNECT failed with sql error '12505'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12505
DbSl Trace: CONNECT failed with sql error '12505'
DbSl Trace: OCI-call 'OCIServerAttach' failed: rc = 12505
DbSl Trace: CONNECT failed with sql error '12505'
(DB) ERROR: DbSlErrorMsg rc = 99
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090121153011

sapinst.log (part)
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20090121153011
ERROR 2009-01-21 15:30:11.125
CJS-30023  Process call 'C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR 2009-01-21 15:30:11.218
FCO-00011  The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|6|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR ( Last error reported by the step :Process call 'C:\usr\sap\PI1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.).

[Former Member · Accepted solution]

Update....

I did this:

LSNRCTL>start

It says "Listener using listener name LISTENER has already been started"

But I guess since it is a Solman listener, it is unable to connect to the PI oracle db.

Regards

[Former Member · Accepted solution]

Basically you have two possibilities, you can have one listener for both systems, or two distinct listeners.

I suggest you have two listeners. As long as you have different OS users for both installations (-> different ORACLE_HOME's), you will only need to make sure, the second listener has not the same port configured, they can both be named LISTENER.

Usually you specify the listener port in sapinst, for example 1528. If you forgot that, you can still change it in $ORACLE_HOME\network\admin -> listener.ora / tnsnames.ora

Best regards, Michael

[Former Member · Accepted solution]

Hi Michael,

Thank you very much for your response....indeed it was a port error.

Unfortunately I did not know how to resolve this error and could not see your post by then. So I ran a new installation and this time I changed the port to 1528...and bingo...it solved the problem! I have completed the installation successfully now.

I am facing a new problem now. The solman instance cannot be seen in the sapmmc...only the PI instance is visible. Let me know if you can resolve this too. The link is [here|;

Thanks

You may have to set ports in the tnsnames.ora and listener.ora file after the installation again. Check [this thread|; for details

Edited by: Prasad Kamath on Jan 22, 2009 7:15 AM