R3trans -d cannot connect to oracle listener with alias name

[Former Member]

We have two systems on our production server host.  One Java and one ABAP, each with its own databaase and listener.  We need to have each listener set up with a unique listener alias name for our HA environment.  We can change the listener.ora files for both instances and change the alias names with no problem using 'LSNRCTL> start LISTENER_<SID>'. The Java system has no issues.

However, testing the ABAP connection with 'R3trans -d' always fails with an ORA-12505 error unless we use the default listener alias name of LISTENER.  We would like to change it to LISTENER_PRD.  Note: I have already seen note 576919 and its associtated notes.

Is there any thing that we can change to have 'R3trans -d' use something other than the default name LISTENER to connect with?

[volker_borowski2]

Hi,

the client usually does not evaluate the listenername.

Only Port, Hostname, and DBNAME/DB-Alias should be relevant.

You should post the relevant *.ora files, so that we can try to detect the misconfiguration.

Also the trans.log from the faulty "R3trans -d" might be of help.

Right now I'd assume a port configuration missmatch.

Volker

[Former Member]

If you have upgraded your Oracle from 10g to 11g, then you need to an entry into <sid>adm "tnsnames.ora" file. Check the tnsnames.ora under <orad>sid account.

[Former Member]

Hello Floyd,

Can you please do the few checks:

1) stop & start listener again.

2) There are two location where listener.ora resides:

     a)  /oracle/<home>/network/admin

     b) /usr/sap/<SID>/SYS/profile/oracle

You can define the location of listener file by setting "TNS_ADMIN" environment variable.

Please check your environment variable & change in respective file.

Regards

Vishal

[Former Member]

Nice try.

There are two tnsnames.ora files.  Hence, the variable TNS_ADMIN.  Both are okay.

There is only one listener.ora file.

What I am looking for is a way to trick R3trans -d into looking for the listener using an alias name other than 'LISTENER'.

[Former Member]

This means your tnsping is working fine for your ABAP system as well??

[Former Member]

Your assumption is absolutely correct.  Tnsping and all other listener testing works fine.  The only thing that does not work is R3trans -d.