Notifications

152 views

Description

"Oracle DB On Unix" pattern in NY has condition to proceed for "on Solaris" ID section that runs when DB is not on Solaris.

The step here:
step {
name = "match we are on solaris"
match {
any {
starts_with {
"SOLARIS"
get_attr {"computer_system.osType"}
}
starts_with {
"LINUX"
get_attr {"computer_system.osType"}
}
}
terminate_op = terminate
}


However, you can have a Oracle DB on a Linux server that is not solaris.
So the wrong ID section runs, when it should run the second one after the solaris ID section.

Steps to Reproduce

In NY run discovery on a linux server that runs Oracle DB.
See the solaris ID section runs when it should not.


Workaround

Workaround:
1. Edit the "Identification for Oracle DB entry point type(s) - no instance on solaris" identity section in "Oracle DB On Unix" pattern
2. In Step 2, remove the following filter: "$computer_system.osType" "Starts With" "LINUX"


Related Problem: PRB1373967

Seen In

SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Risk Management - New York 2019 Q3
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6

Fixed In

Orlando

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-06-01 05:10:46
Published:2020-04-01