BMC Remedy Single Sign-On - Unable to upgrade BMC RSSO due to ORA 12505

Version 5
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    Remedy Single Sign On


    Single Sign On




    During RSSO upgrade, the installer complains of a SID not being found, however you may not using SID's in your environment but Service Names.

    Here is a log portion of the rsso install logs where you can see as a reference besides the error message "Unable to upgrade due to ORA-12505" in the installer.

    (May 15 2019 04:55:09.581 PM -0400),CONFIG,com.bmc.install.task.InstallationPropertiesHelper,
    (May 15 2019 04:55:09.581 PM -0400),INFO,com.bmc.install.product.remedysso.validator.RemedySSODbUsersValidationTask,
      LOG EVENT {Description=[Validation error],Detail=[DB_UNABLE_USER_CONNECT]}
    (May 15 2019 04:55:09.991 PM -0400),CONFIG,com.bmc.install.product.base.project.runner.ProjectRunner,

    Alternatively, below is a portion message you may find if you run the installer in silent mode:

    LOG EVENT {Description=[JVM launcher command],Detail=["/usr/bin/java" -Xmx512m -classpath "/opt/bmc/tmp/RSSO1902/BMCRemedySSO/Disk1/" "-Dsun.java2d.noddraw=true" "-Dswing.volatileImageBufferEnabled=false" "" "-Xdebug" "-Xrunjdwp:server=y,transport=dt_socket,address=12333,suspend=n" -Dbmc.install.LAUNCHER_EXECUTABLE="/opt/bmc/tmp/RSSO1902/BMCRemedySSO/Disk1/" -jar "/opt/bmc/tmp/RSSO1902/BMCRemedySSO/Disk1/setup.jar" "install" -i silent -DOPTIONS_FILE=/opt/bmc/tmp/RSSO1902/options.txt]}
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Aborted (core dumped)
    (May 15 2019 06:32:18.188 PM -0400),CONFIG,Command return code,
    LOG EVENT {Description=[134]}


    This is a known issue in the RSSO installer with Oracle database which does not recognizes the service names.


    In order to overcome this error you need to execute the following steps:

    1. Open this file /opt/bmc/RemedySSO/RemedySSOInstalledConfiguration.xml to modify the next steps. (Always take a backup of the file prior the update in a different folder location as a health practice).

    2. Switch this setting DB_ORACLE_SID to DB_ORACLE_SERVICE with it's according Service Name. With the correct entry. e.g. jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=XXXXXXXXXXX)(PORT=XXXX))(CONNECT_DATA=(SERVER=XXXXXXXXXXX)(SERVICE_NAME=XXXXXXXXXXX)))

    3. Correct the JDBC connection string  <name>DB_JDBC_URL</name>

    5. Save the file.

    6. You could either skip back and skip next to ensure the installer pulls the jar files and reads the modified xml OR you can quit the installer and remove the rsso related files in /tmp (Linux) %Temp% (Windows) that are generated by the installer and run the installer again.



    Article Number:


    Article Type:

    Solutions to a Product Problem

      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles