Scan hanging on DB2 for IBM series

book

Article ID: 159921

calendar_today

Updated On:

Products

Data Loss Prevention Network Discover

Issue/Introduction

Scan for DB2 for IBM series has been setup and configured as per KB TECH221236.

However, in order to delimit results from database to one set of library tables within, additional filters were added to the connection string:

db2fori://hostname:library.table

The scan starts and even generate incidents but never completes.

 

 

The following may be present in the ScanDetails log, indicating that FileReader is being restarted every 17 minutes, due to heartbeat timeout:

"Feb 15, 2012 8:17:15 AM","INFO","","STARTED_SCAN","","0","","","",""
"Feb 15, 2012 8:17:15 AM","INFO","","STARTED_SCAN","","0","","","",""
"Feb 15, 2012 8:17:15 AM","INFO","NameOfScan - library.table 02/14/12 - 3:17 PM","STARTED_SEGMENT","db2fori://hostname:library.table","0","","","",""

"Feb 15, 2012 8:34:16 AM","INFO","","STARTED_SCAN","","0","","","",""
"Feb 15, 2012 8:34:16 AM","INFO","","STARTED_SCAN","","0","","","",""
"Feb 15, 2012 8:34:16 AM","INFO","NameOfScan - library.table 02/14/12 - 3:17 PM","STARTED_SEGMENT","db2fori://hostname:library.table","0","","","",""

Resolution

The configuration of the connection string in not correct and is causing the timeouts.

In order to delimit items scanned, use the Include Filter, with the following format:

The connection string for the target will be as per TECH221236: 

db2fori://hostname

And in the include filter put:

db2fori:*|*.table

 

This should allow Discover to map the intended targets and complete the scan.