 Hi and welcome to this video tutorial on how to configure a standalone Oracle Database environment using TrueSight console. Login to the TrueSight console and click on infrastructure policies in the configuration tab and next click on create policy. In this screen enter the policy name, the agent host name where this policy will be applied and enable the policy. Click on add monitoring configuration. Here select the monitoring solution as Oracle Enterprise Database, the monitor profile is Oracle environment monitoring and the monitor type is Oracle standalone database. Also from here you have an option to enable logging for the global monitoring settings. Click on add to provide the environment configuration details. Here enter a unique environment name for monitoring the Oracle Database. A container gets created with this environment name which will hold all the database instances configured part of this environment. The Oracle standalone database monitor type has three sections. The monitoring categories and environment settings sections are applicable for all the standalone instances added part of this unique environment. We'll start with the environment settings configuration first. The environment settings configuration has two sections. From here you can enable logging for this environment and all the standalone instances configured part of this environment. The device mapping consolidates the monitoring at a device level. By default it is enabled and the patrol for Oracle Enterprise Database host appears as a device in the TrueSight console. You can disable this feature to display all the instances and parameters of the game under the patrol agent device. In the java collector settings you'd need to provide a path to the java home. If the java home has been configured part of your patrol agent default account profile then you can leave it with a default value else you'd need to provide the path to the java home. Optionally you can also provide any JVM arguments to start the java collector if needed. The java OS credentials can be left blank if the patrol default account has execute privileges on java binaries else please provide the credentials which has privileges to execute java and start the java collector. In the collection settings section you can specify the availability collection interval, the data collection interval and the long-running data collection queries duration in minutes. If any of the data collection queries are taking more than the time specified in here the game will cancel the queries execution and those queries will be reported in the long-running queries attribute. After configuring the environment settings please proceed to the monitoring categories section. From here please select the monitoring categories that you'd like to monitor. Select this monitoring category to be able to monitor the tablespaces. You can also select the filtering mode in here to include or exclude tablespaces from being monitored. And based on the filtering mode you have to provide the tablespace names in here separated by a comma. Select this monitoring category to be able to monitor the Oracle Database jobs. Here you can specify the duration in minutes for the long-running jobs and the overdue jobs. Now let's go to the standalone instance configuration section and click on add. Here we have two sections one is Oracle connection details the other one is Oracle custom SQL queries. In the Oracle connection details you need to provide details of the Oracle standalone database host like the host name or the IP address port number to connect to the database instance. In the connection method you can either use the service name or the Oracle set here I have used the service name and also you can select connect assist DBA to be able to connect to the database using a assist DBA privileged user but BMC recommends you to use a designated monitoring user. In the Oracle custom SQL queries section please click on add to be able to add a custom SQL query for monitoring you need to provide a name for the SQL query and the SQL query in here and also you need to specify the collection interval in minutes. You can also select this checkbox to be able to get the query result as an annotation on the number of records metric but this is only applicable when your query is returning more than one row. Now I will add one more database for monitoring and this time I have used the Oracle SID for the connection method. Now let's click on OK and set the policy. To verify if the configuration is correct please expand the monitoring tab and click on the devices to see the results of the configured policy. Click on the patrol agent device or the Oracle database host device depending on the device mapping selection in the policy. The monitoring hierarchy should be complete. Review the Oracle database instance level, instance status and the instance configuration status. If the instance doesn't appear or the environment setting needs to be updated please refer to the environment level configuration status and the monitor status at the patrol agent device level. For more details log on to docs.bmc.com. Thanks for watching.