Error "Could not connect to database"

Technical Articles ID: KB90906
Last Modified: 2023-05-04 07:21:14 Etc/GMT

Environment

Data Loss Prevention Discover (DLP Discover) 11.x

Oracle Database 12c

Problem

While scanning an Oracle Database version 12c, the following error is recorded in operation events:

Could not connect to database.

The details of the event show the following error message:

DB vendor errors(2): E-0: EN 0x800440E31 Native error 0 [McAfee][ODBC Oracle Wire Protocol

Cause

The error code 0x800440E31 means that the timeout period has expired. It can happen because of one of the following reasons:

The database is busy
There's a network issue when the DLP Discover crawler tries to access the database

Solution

This kind of intermittent behavior is considered normal. DLP Discover has a mechanism to handle such intermittent errors. The DLP Discover crawler retries multiple times over the course of 10 minutes. When the crawler reaches the 10-minute timeout period and is unable to continue the scan, the crawler stops trying to start the scan. If during the 10-minute timeout period the crawler is successful, the scan continues until completed.

Workaround

Technical Support recommends that you run scans outside of normal business hours to decrease the likelihood of a timeout.

Affected Products

Data Loss Prevention Discover 11.x

Languages:

This article is available in the following languages:

Knowledge Center

Error "Could not connect to database"

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Title

Title

Knowledge Center

Error "Could not connect to database"

Environment

Problem

Cause

Solution

Workaround

Affected Products

Languages:

Choose your region

Title

Title