Clarity

 View Only
  • 1.  Clarity can not connect to Oracle DB after security patch

    Posted Sep 06, 2024 04:28 AM
    Edited by Sebastian Ryborz Sep 06, 2024 04:30 AM

    Hi All,

    we are experiencing a broken database connection from Clarity v 16.0.2 after a Oracle 19 security patch was applied.

    It looks like the OEM JDBC driver (DataDirect) is the troublemaker here, and we are looking for approaches to re-enable our environment, without a roll-back of the db-patch.

    DataDirect lists this behavior on their website, though we couldn't find a workaround besides of upgrading the JDBC-package yet, which is OEM.

    Has someone experienced the same problem, and does have an approach to share how to re-enable the db-connection for Clarity?

    Cheers,

    Sebastian



  • 2.  RE: Clarity can not connect to Oracle DB after security patch

    Broadcom Employee
    Posted Sep 06, 2024 05:00 AM

    Hi Sebastian

    Looking at the situation you have option

    1. Download the latest data direct driver and use
    2. Roll back the Oracle patch
    3. Plan an upgrade to latest version 

    Note: Clarity migrated to native drivers starting version 16.0.3 



    ------------------------------
    Thanks & Regards
    Suman Pramanik
    Senior Principal Support Engineer | Agile Operations Division
    Broadcom Software
    ------------------------------



  • 3.  RE: Clarity can not connect to Oracle DB after security patch

    Posted Sep 06, 2024 05:20 AM

    Hi Suman,

    many thanks for your quick reply.

    Assuming we'd opt for "1. Download the latest data direct driver and use", is there a guide available how to apply it?

    The bundled DataDirect driver (part of original 16.0.2 as I understand) would need to be replaced by a not-OEM-DataDirect driver, right?

    Thank you and best regards,

    Sebastian

    P.S.

    Basically we are on the way to upgrade to recent release of Clarity, though the Oracle DB patch was faster than us ;)

    Now we're looking for options to re-enable the current environment (in a supported way) 

    V. 16.0.3 (as a required intermediate upgrade step) is an option, though means a tremendous effort with testing, assuming, the setup-script can establish connection to the patched Oracle DB.

    Ideally the current setup could be re-enabled, so the planned upgrade could be processed at once (16.0.3, 16.1.3, 16.2.3).




  • 4.  RE: Clarity can not connect to Oracle DB after security patch

    Broadcom Employee
    Posted Sep 06, 2024 08:13 AM

    There will be a file called c-oracle.jar under clarity_home\bin, and when we packaged data direct we took the driver and build the jar. So if the plan 1 then the driver to be downloaded and embeded to the c-oracle.jar



    ------------------------------
    Thanks & Regards
    Suman Pramanik
    Senior Principal Support Engineer | Agile Operations Division
    Broadcom Software
    ------------------------------



  • 5.  RE: Clarity can not connect to Oracle DB after security patch

    Posted Sep 06, 2024 09:38 AM

    Hi Suman,

    many thanks! This sounds quite straight forward.

    Best regards,

    Sebastian