Forum Discussion

casteeb's avatar
casteeb
Icon for Neophyte rankNeophyte
8 months ago

Remote DB connections via Oracle SQLnet

While Logic Monitor seems determined that it needs to "connect" to a remote host to gather data, in the case of Oracle DB up / down testing it's much easier to just perform a remote connection via SQ...
casteeb's avatar
casteeb
Icon for Neophyte rankNeophyte
8 months ago

Thanks Stuart, we worked on implementing this yesterday. Found a lot of good scripting examples in the built-in Oracle code.

Added the DB list to the server, added a simple check_oracle Datasource script to the My Module Toolbox on the collector which just echos the list and returns 0 , in check_oracle DS script we set AppliesTo (checked with Launch IDE and validated that resolves to the specific server server name and IP where we put the list). But that Data source is still stuck on the "Not in use" status. I'm missing something ....

  • Anonymous's avatar
    Anonymous
    8 months ago

    You should have one DS with two scripts. If you have a script to automatically discover the list of database names (check_oracle), that seems like it would be your discovery script. Then your collection script would actually check to see that each instance discovered in your discovery script can be connected to.