Connection Details


Section	Field	Description
Create New Collector	Database Type	The database type that you want to monitor.
	Agent	The Database Agent that manages the collector.
	Collector Name	The name you want to identify the collector by.
Connection Details	Hostname or IP Address	The hostname or IP address of the machine that your database is running on.
	Listener Port	The TCP/IP address of the port on which your database communicates with the Database Agent
	SID or Service Name	The SID or service name of the Oracle instance you want to monitor. For CDB (container database) monitoring, provide the CDB service name and for PDB (pluggable database) monitoring, provide the PDB service name.For PDB (pluggable database) monitoring, the service name must be present in all the nodes that have PDB so that all the nodes get monitored.
	Custom JDBC Connection String	The JDBC connection string generated by the database agent, for example, `jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=`. You can also specify a custom connection string, which is useful for setting custom authentication options. When using connection string for Kerberos, ensure that you select the LDAP/Kerberos option under Advanced Options.
Database Credentials	Username	The name of the user who is connecting to and monitoring the database through the Database Agent. The user should have the permissions described in User Permissions for Oracle.
	Password	The password of the user who is connecting to and monitoring the database through the Database Agent.
	Cyberark	Click to enable CyberArk for database username and password. When CyberArk is enabled, information about Application, Safe, Folder, and Object is required to fetch the username and password for your database. To use CyberArk with Database Visibility, you must download the JavaPasswordSDK.jar file from the CyberArk web site and rename the file to cyberark-sdk-9.5.jar. Then, you must copy the JAR file to the lib directory of the database agent zip file.
	HashiCorp Vault	See Configure the HashiCorp Vault.
Advanced Options	Sub-Collectors	Click to monitor multiple database instances in a consolidated view, and aggregate metrics of multiple databases. To monitor a custom cluster, you can add additional hostname or IP address, and port details for each sub-collector. You can add up to a total of 29 sub-collectors. Thereby, 30 databases can be monitored in a custom cluster. In addition to the licenses consumed by the main collector, each sub-collector consumes one or more licenses, depending on the database type. Note: All connection parameters other than the hostname or IP address, and port details of the sub-collector are the same as the main collector. If you want to specify different parameters for the sub–collectors, while creating or editing the collector configuration, you can do that only via the Create Collector API. You cannot convert a custom cluster collector to a standalone collector. If you want to monitor a standalone database, delete the entire custom cluster collector and create a fresh standalone collector. However, note that deleting the custom cluster collector will delete all its historical data.
	Connection Properties	Click to add a new JDBC connection property or edit an existing property for relational databases. For monitoring the database using Kerberos authentication, follow the instructions mentioned at Monitor Oracle Databases Using Kerberos Authentication.
	Exclude Schemas	The schemas that you want to exclude, separated by commas.
	SSL Connection	Click to enable the SSL connection. You can use SSL Connection for authentication and signing credentials. Truststore Location: location of the SSL certificate that is stored on the DB Agent host Truststore Type: type of truststore used for SSL certificate. There are two truststore types:PKCS12 (default)SSO: enables auto-login. If you use SSO, you only need to provide the truststore location and truststore type. Truststore Password: password for SSL certificate. If the SSL_CLIENT_AUTHENTICATION parameter is set to true in listener.ora and sqlnet.ora, then click the Enable SSL Client Authentication box. Keystore Location: location of the SSL certificate on the DB Agent host Keystore Type: type of SSL certificate Keystore Password: password of SSL certificate
	LDAP/Kerberos	Use LDAP/Kerberos authentication to manage the database user and the host user passwords.
	Monitor Operating System	See this page for more details, Configure the Database Agent to Monitor Server Hardware.

Documentation

Connection Details