Starting from TKU September 2020 Database Detail node type was updated to contain DB Server type. (DRDC1-14748) e.g. SQL Database Schema type was changed to MySQL(Percona, MariaDB, Aurora, Infobright) Database Schema. Please be aware that this update may impact CMDB syncing.
The goal of the Oracle MySQL Server Database Detail pattern is to obtain the list of Databases being managed by the MySQL Server, and to obtain (optionally, and disabled by default) the list of Tables within these databases.
The patterns will not by default return the list of all tables within the discovered databases as this can have a marked impact on discovery of hosts with large database installations
The information is then stored within the Atrium Discovery Model as DatabaseDetail Nodes. In Atrium Discovery 8.3 and later, the DatabaseDetail node has additional attributes added which permit easy mapping by the CMDB sync mechanism to the BMC_Database CIs in Atrium CMDB.
The option to set the default port no longer exists in the MySQL Database Detail pattern.
The MySQL Database Detail pattern behavior is now as follows:
The pattern executes the following SQL Queries.
The pattern only runs the latter query (and creates the table nodes) if the retrieve_tables configuration option is enabled
Discovery by file query is only attempted if discovery by a database credential fails and the use_listdir configuration option is enabled. By default the use_listdir option is enabled
The pattern obtains a list of all subdirectories of the db_path. If any of these subdirectories contains a database file the patterns assumes this corresponds to a database with the name of the subdirectory, and creates a Database node. They files the pattern looks for are:
So, for example, if /opt/MySQL/data has a subdirectory "BigData" and file /opt/MySQL/data/BigData/db.opt exists then a Database node will be created with instance name "BigData"
We do not attempt to retrieve table information when we discover database information by a file query