Clarity

Expand all | Collapse all

Upgrade Failed- error (2): Connection Refused

  • 1.  Upgrade Failed- error (2): Connection Refused

    Posted Dec 14, 2012 07:20 AM
    Hi,

    Our upgrade from 12.0.4 to 13.0.1 is failing with error (from install.log):
    Command: install database schema file
    To URL:
    jdbc:clarity:oracle://localhost:1521;SID=NIKU;BatchPerformanceWorkaround=true;
    InsensitiveResultSetBufferSize=0;ServerType=dedicated;supportLinks=true
    As user: niku
    For vendor: oracle

    Process:
    D:\DVD01135604M\install-packages\12.1.1\upgrade-repack.12.1.1.1208\upgrade\12.
    1.1\preupgrade/PREUPGRADE_VALIDATE_FIN_PLANS_DATA.xml

    Total time: 0H:0M:4S
    Exception in thread "main" java.sql.SQLException: [CA Clarity][Oracle JDBC
    Driver]Error establishing socket to host and port: localhost:1521. Reason:
    Connection refused: connect.

    In properties.xml though, we have only one database entry (for port 1524);
    following entry is being made itself for port 1521:

    added by us:[b] <database id="CLARITY" useURL="false" jndiDatabaseId="jdbc/NikuDS"
    vendor="oracle" serviceName="CLARITY" serviceId="CLARITY" instanceName=""
    driver="com.ca.clarity.jdbc.oracle.OracleDriver"
    url="jdbc:clarity:oracle://10.10.4.9:1524;SID=CLARITYU;BatchPerformanceWorkaro
    und=true;InsensitiveResultSetBufferSize=0;ServerType=dedicated;supportLinks=tr
    ue" username="niku1" password="nikupw" schemaName="CLARITY"/>

    added in properties.xml automatically after installation begins:
    <database id="Niku" jndiDatabaseId="jdbc/NikuDS" vendor="oracle"
    serviceName="niku" serviceId="niku"
    driver="com.ca.clarity.jdbc.oracle.OracleDriver"
    url="jdbc:clarity:oracle://localhost:1521;SID=NIKU;BatchPerformanceWorkaround=
    true;InsensitiveResultSetBufferSize=0;ServerType=dedicated;supportLinks=true"
    username="niku" password="niku" schemaName="niku"/>

    and with the above the values the connection is refused and the upgrade fails.

    Please help as we are unable to proceed further.

    regards,
    Uruj


  • 2.  RE: Upgrade Failed- error (2): Connection Refused

    Posted Dec 14, 2012 07:44 AM
    1521 is the default port for Oracle client.

    Is you Oracle client set to use the same port as you CSA and properties.xml?
    Is that port being listened (netstat -an)
    Can you connect to Oracle with other sofware?



    Martti K.


  • 3.  RE: Upgrade Failed- error (2): Connection Refused

    Posted Dec 17, 2012 03:05 AM
    Were you able to do as suggested by Martti ?

    "1521 is the default port for Oracle client.

    Is you Oracle client set to use the same port as you CSA and properties.xml?
    Is that port being listened (netstat -an)
    Can you connect to Oracle with other sofware?"

    NJ


  • 4.  RE: Upgrade Failed- error (2): Connection Refused

    Posted Dec 17, 2012 05:44 AM
    Thanks,

    we verified everything and were using same IP and correct port (as were able to connect).

    Adding the below line,

    <database id="" useURL="false" jndiDatabaseId="jdbc/DS" vendor="oracle" serviceName="" serviceId="" instanceName="" driver="com.ca.clarity.jdbc.oracle.OracleDriver" url="jdbc:clarity:oracle://:;SID=;BatchPerformanceWorkaround=true;InsensitiveResultSetBufferSize=0;ServerType=dedicated;supportLinks=true" username="" password="" schemaName=""/>

    had solved the purpose and now its not failing at that point and has moved forward. Any inputs?

    Regards,
    Uruj


  • 5.  RE: Upgrade Failed- error (2): Connection Refused
    Best Answer

    Posted Dec 17, 2012 02:39 PM
    D:\DVD01135604M\install-packages\12.1.1\upgrade-repack.12.1.1.1208\upgrade\12.
    Sounds like it failing in the upgrade to 12.1 step.
    What your jdk version and does JAVA_HOME point to that.
    If you are using Tomcat is that the version for 12.1 (apache-tomcat-6.0.26)

    Can you access NSA/CSA (even if you only have partially installed system) to see if you get the database status.
    If you cannot the you could still try to get if from command line.
    See
    98498210
    with a copy of
    healthcheck.xml
    as in the thread
    so that the original remains intact.

    I could also be simpler to get the install for v12.1 and update with that first and when that is successfull then to v13


    Martti K.


  • 6.  RE: Upgrade Failed- error (2): Connection Refused

    Posted Mar 13, 2013 04:54 PM
    Did you ever get this fixed?

    Martti K.


  • 7.  RE: Upgrade Failed- error (2): Connection Refused

    Posted Mar 14, 2013 02:12 AM
    Were you able to get thro' with the upgrade ?

    NJ


  • 8.  RE: Upgrade Failed- error (2): Connection Refused

    Posted May 02, 2013 01:47 AM
    Yes,

    Thanks all. It was resolved.

    Uruj


  • 9.  RE: Upgrade Failed- error (2): Connection Refused

    Posted May 02, 2013 01:58 AM
    Would you like to share the secret?


    Martti K.


  • 10.  RE: Upgrade Failed- error (2): Connection Refused

    Posted May 02, 2013 03:12 AM
    Hi,

    It was issue due to the database team.. some discrepancy in the details provided...

    Uruj


  • 11.  RE: Upgrade Failed- error (2): Connection Refused

    Posted May 02, 2013 03:29 AM
    Thanks,

    My symphaties. Every now and then it happens that the Clarity admin does not have db and OS rights and the ones that have them made a booboo.


    Martti k.


  • 12.  RE: Upgrade Failed- error (2): Connection Refused

    Posted Mar 14, 2014 08:02 AM
    uruj:
    Thanks, we verified everything and were using same IP and correct port (as were able to connect). Adding the below line, <database driver="com.ca.clarity.jdbc.oracle.OracleDriver" instancename="" jndidatabaseid="jdbc/DS" password="" schemaname="" serviceid="" servicename="" url="jdbc:clarity:oracle://:;SID=;BatchPerformanceWorkaround=true;InsensitiveResultSetBufferSize=0;ServerType=dedicated;supportLinks=true" username="" useurl="false" vendor="oracle"></database>had solved the purpose and now its not failing at that point and has moved forward. Any inputs? Regards, Uruj




    Hi Uruj,

    Thanks for sharing this solution.

    We were getting the same error and this provided the perfect solution. :)