Oracle DB on Unix Discovery Pattern uses sqlplus executable version rather than actual oracle versionDescriptionThe version of the Oracle database being discovered via the 'Oracle DB On Unix' pattern is not necessarily that of the actual database as it is taking the results of 'sqlplus -v', which is the version of the sqlplus installation.Steps to Reproduce Run a Horizontal Discovery against an Oracle database.Notice that the returned version is that of the sqlplus executable rather than the actual database. These are not always the same! The step is:Pattern Designer > Discovery Patterns >"Oracle DB on Unix""Identification for Oracle DB entry point type(s)"Step 14: Get version"export ORACLE_HOME=" + $ora_home_exe + ";" + $ora_home_exe + "/bin/sqlplus -v " The command sqlplus -v only gets the version of sqlplus - this can be different if for instance $TWO_TASK is used and a lower or higher version of the database may actually be used. The sqlplus statement to get the actual db version is:Select * from v$version where banner like 'Oracle%'; For example, the discovered version is '19.0.0.0.0' but the expected version is '19.7.0.0.200414' as they have added patches to their Oracle database.WorkaroundAdded new steps to fetch version directly by querying the DB and updating the version on the CI, update set attached. After update set is applied make below additional change. On steps "Get version directly from Oracle DB" & "Failover Get version directly from Oracle DB using SID" change the parsing strategy to Regex and use this "Version (\S+)" regex with same "version_db" var name on both the steps.Related Problem: PRB1488145