Automic Workload Automation

  • 1.  Two CONN DB Created

    Posted Feb 19, 2018 09:50 AM
    Hi,

    We noticed that  we have an UC4 DEV client XXXX  has at least 2 connections using production IP adresses.

    We have identified 2 connections so far:
    CO.CONN.FTPAGENT.ODIDB
    CO.CONN.FTPAGENT.MOMDB

    It is possible that there are more issues like this in this UC4 client?

    Thanks
    Noah Gochuico


  • 2.  Two CONN DB Created
    Best Answer

    Posted Feb 19, 2018 09:56 AM
    Shouldn't you ask this questions your OPS- DEV- or Admin colleagues, should you?

    cheers, Wolfgang


  • 3.  Two CONN DB Created

    Posted Feb 19, 2018 09:56 AM
    There is nothing stopping someone creating a CONN object to point to Production from DEV.

    This query will tell you all the CONN objects in your UC4 System

    select OH_Name, ocv_vname,   DBMS_LOB.substr(ocv_value, 50) 
    from uc4.OH a, uc4.OCV b
    where a.OH_Idnr = b.OCV_OH_Idnr 
    and a.OH_OTYPE = 'CONN'
    and (ocv_vname = 'db.name' or ocv_vname = 'DbUserid')
    order by 1


  • 4.  Two CONN DB Created

    Posted Feb 19, 2018 10:05 AM
    Hi

    Thanks for the quick response.

    Hi Wolfgang,

    Not yes, but i will ask the OPS-DEV and to confirm what is purpose of creating two conn db.

    Thanks again.
     




  • 5.  Two CONN DB Created

    Posted Feb 19, 2018 01:17 PM
    Yeah - good attempt!

    From Automic side - its not possible to check or interpret the target environments - if one creates a connection to a "wrong" server or DB or any target system....

    cheers, Wolfgang