ORA-12505, TNS:listener does not currently know of SID given in connectdes - Weblogic

This is a discussion on ORA-12505, TNS:listener does not currently know of SID given in connectdes - Weblogic ; Environment: WLS 8.1 On Wintel; Oracle 10g on Solaris. <br> In our development environment, we have setup a the following line in our W= indows hosts file (C:\WINNT\system32\drivers\etc\<b>hosts</b>) <br> <b>192.168.1.123 virtual-db</b> <br> In the development environment, the database is also ...

+ Reply to Thread
Results 1 to 2 of 2

ORA-12505, TNS:listener does not currently know of SID given in connectdes

  1. Default ORA-12505, TNS:listener does not currently know of SID given in connectdes

    Environment: WLS 8.1 On Wintel; Oracle 10g on Solaris.
    <br>
    In our development environment, we have setup a the following line in our W=
    indows hosts file (C:\WINNT\system32\drivers\etc\<b>hosts</b>)
    <br>
    <b>192.168.1.123 virtual-db</b>
    <br>
    In the development environment, the database is also on Wintel and everythi=
    ng works fine.
    <br>
    In our test & production environments, with the database on Solaris; we get=
    the following error:
    <br>
    <Jan 3, 2006 2:13:06 PM EST> <Error> <JDBC> <BEA-001150> <Connection Pool "=
    JMSDBPool" deployment failed with the following error: 0:Could not create p=
    ool connection.
    The DBMS driver exception was: Listener refused the connection with the fo=
    llowing error:
    <b>ORA-12505, TNS:listener</b> does not currently know of SID given in conn=
    ect descriptor
    The Connection descriptor used by the client was: <b>virtual-db:1521:devdb2=
    5</b>
    <br>
    (unless we replace virtual-db with the actual IP address in the java config=
    uration files).
    <br>
    Ie: With Windows to Windows the virtual-db ipaddress is successfully replac=
    ed before trying to connect to the server (TNS listener). With windows to s=
    olaris the virtual-db ipaddress of the host file is not successfully replac=
    ed. We typically don't have the Oracle client installed on the windows jav=
    a application server.
    <br>
    Any ideas as to how to fix the problem?
    <br>
    More generally, I'm looking for a way where, when swithing databases in the=
    test environment (windows/unix) I only need to change the database ip addr=
    ess in one place - instead of in several places within the configuration fi=
    les.
    <br>
    Any suggestions (of solutions known to work?)
    <br>
    Thanks.

  2. Default Re: ORA-12505, TNS:listener does not currently know of SID given inconnect des

    John Slaman wrote:


    > Environment: WLS 8.1 On Wintel; Oracle 10g on Solaris.
    > <br>
    > In our development environment, we have setup a the following line in ourWindows hosts file (C:\WINNT\system32\drivers\etc\<b>hosts</b>)
    > <br>
    > <b>192.168.1.123 virtual-db</b>
    > <br>
    > In the development environment, the database is also on Wintel and everything works fine.
    > <br>
    > In our test & production environments, with the database on Solaris; we get the following error:
    > <br>
    > <Jan 3, 2006 2:13:06 PM EST> <Error> <JDBC> <BEA-001150> <Connection Pool"JMSDBPool" deployment failed with the following error: 0:Could not createpool connection.
    > The DBMS driver exception was: Listener refused the connection with the following error:
    > <b>ORA-12505, TNS:listener</b> does not currently know of SID given in connect descriptor
    > The Connection descriptor used by the client was: <b>virtual-db:1521:devdb25</b>
    > <br>
    > (unless we replace virtual-db with the actual IP address in the java configuration files).
    > <br>
    > Ie: With Windows to Windows the virtual-db ipaddress is successfully replaced before trying to connect to the server (TNS listener). With windows tosolaris the virtual-db ipaddress of the host file is not successfully replaced. We typically don't have the Oracle client installed on the windows java application server.
    > <br>
    > Any ideas as to how to fix the problem?
    > <br>
    > More generally, I'm looking for a way where, when swithing databases in the test environment (windows/unix) I only need to change the database ip address in one place - instead of in several places within the configuration files.
    > <br>
    > Any suggestions (of solutions known to work?)
    > <br>
    > Thanks.



    Hi John. Please show me the pool definition. The problem is somewhere between the
    JDBC driver, OS, and DBMS. I can at least help to make a tiny standalone program
    that duplicates the problem.
    Joe

+ Reply to Thread