TNS Listener Error During CE 7.2 Install Phase "Import Java Dump"

Question

Hi All,
We are installing a new CE 7.2 system on AIX 6.1 with Oracle 10.2.0.4
(system name JDQ). We are receiving the following error during
installation phase "Import Java Dump:"
Oct 11, 2010 12:44:50 PM com.sap.inst.dbtools
[Thread[main,5,main]] Fatal:
com.sap.inst.common.exception.DBConnectionException:
java.sql.SQLException: Listener refused the connection with the
following error:
ORA-12505, TNS:listener does not currently know of SID given in connect
descriptor
at com.sap.inst.common.db.DBConnection.connect
(DBConnection.java:157)
at com.sap.inst.jload.Jload.main(Jload.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.offline.OfflineToolStart.main
(OfflineToolStart.java:161)
We chose "Typical" for the installation type and sapisnt chose port
1527 for the Oracle listener port by default. We are installing JDQ on
a server where other SAP instances are already installed.
Unfortunately, port 1527 is already in use by one of the other SAP
systems for its Oracle listener. We have tried the following to
resolve the error:
1) Changed listener port for JDQ
a. Changed the following files for JDQ to use port 1530 instead of
1527:
$ORACLE_HOME/network/admin/listener.ora
$ORACLE_HOME/network/admin/tnsnames.ora
/sapmnt/JDQ/profile/oracle/tnsnames.ora
b. Restarted the JDQ database and listener, then clicked Retry
c. Did not work. Exited and restarted the install, but this did
not work, either.
2) Changed listener name for JDQ
a. Changed the following files for JDQ to use listener
name "LISTENER_JDQ" instead of the default name of "LISTENER":
$ORACLE_HOME/network/admin/listener.ora
b. Restarted the JDQ database and listener, then clicked Retry
c. Did not work. Exited and restarted the install, but this did
not work, either.
d. Changed the listener name back to "LISTENER" and restarted the
DB and listener
3) Changed installation files containing port 1527
It looks like the installation saves the input parameters in files in
the instllation directory. After we changed the JDQ environment to use
the 1530 port, we thought maybe the install was getting 1527 from one
of the installation files. Therefore we tried the following:
a. Used command "find . -xdev -type f -exec grep -l -w 1527 {} \;"
to obtain a list of files containing port 1527.
b. Backed up these files
c. Edited these files, changing 1527 to 1530. Files modified
include the following:
control.xml
inifile.2.xml
inifile.3.xml
inifile.xml
keydb.2.xml
keydb.xml
summary.html
d. Clicked Retry, but still got the error
e. Exited the installlation and restarted it. We are still
getting the error.
4) I know that for Java systems, the listener port is stored in the
Secure Store. The SecStore.key and SecStore.properties files have been
installed in directory /usr/sap/JDQ/SYS/global/security/data; however,
configtool does not yet exist under /usr/sap/JDQ/J01; therefore I
cannot see whether port 1527 has been placed in the Secure Store.
Therefore, we did not take any action here.
What do we need to do to resolve the error?
Thanks in advance for any help you can provide.
Tommye

Answer 1

HI ,
Could you please let us know how did you edit the secstore file without configtool ? How did you resolve the issue? I am facing the exact issue now..Please advice .
Regards,
Nibu Antony