Oracle Database Listener protocol configuration options

To remotely collect log files that are generated from an Oracle database server, configure a log source to use the Oracle Database Listener protocol source.

The Oracle Database Listener protocol is an outbound/active protocol.

Before you configure the Oracle Database Listener protocol to monitor log files for processing, you must obtain the directory path to the Oracle database log files.

The following table describes the protocol-specific parameters for the Oracle Database Listener protocol:

Table 1. Oracle Database Listener protocol parameters
Parameter	Description
Protocol Configuration	Oracle Database Listener
Log Source Identifier	Type the IP address, host name, or a unique name to identify your log source.
Server Address	The IP address or host name of your Oracle Database Listener server.
Domain	Type the domain for your Oracle Database Learner server. This parameter is optional if your server is not in a domain.
Username	Type the user name that is required to access your server.
Password	Type the password that is required to access your server.
Confirm Password	Type the password that is required to access the server.
Log Folder Path	Type the directory path to access the Oracle Database Listener log files.
File Pattern	The regular expression (regex) that identifies the event logs.
Force File Read	Select this check box to force the protocol to read the log file when the timing of the polling interval specifies. When the check box is selected, the log file source is always examined when the polling interval specifies, regardless of the last modified time or file size attribute. When the check box is not selected, the log file source is examined at the polling interval if the last modified time or file size attributes changed.
Recursive	If you want the file pattern to search sub folders, use this option. By default, the check box is selected.
SMB Version	Select the version of SMB that you want to use. AUTO Auto-detects to the highest version that the client and server agree to use. SMB1 Forces the use of SMB1. SMB1 uses the jCIFS.jar (Java™ ARchive) file. Important: SMB1 is no longer supported. All administrators must update existing configurations to use SMB2 or SMB3. SMB2 Forces the use of SMB2. SMB2 uses the jNQ.jar file. SMB3 Forces the use of SMB3. SMB3 uses the jNQ.jar file. Note: Before you create a log source with a specific SMB version (for example: SMBv1, SMBv2, and SMBv3), ensure that the specified SMB version is supported by the Windows OS that is running on your server. You also need to verify that SMB versions is enabled on the specified Windows Server. For more information about which Windows version supports which SMB versions, go to the Microsoft TechNet website (https://blogs.technet.microsoft.com/josebda/2012/06/06/windows-server-2012-which-version-of-the-smb-protocol-smb-1-0-smb-2-0-smb-2-1-or-smb-3-0-are-you-using-on-your-file-server/ ). For more information about how to detect, enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server, go to the Microsoft support website (https://support.microsoft.com/en-us/help/2696547/detect-enable-disable-smbv1-smbv2-smbv3-in-windows-and-windows-server).
Polling Interval (in seconds)	Type the polling interval, which is the number of seconds between queries to the log files to check for new data. The default is 10 seconds.
Throttle events/sec	The maximum number of events the Oracle Database Listener protocol forwards per second.
File Encoding	The character encoding that is used by the events in your log file.