Catalog Based-scan in running state

Few if the systems was reporting to Missing soft scan hence we killed wscan process on these systems and initiate scan again. After which we found we got error 137 on resource utilization and software identification san. Status of Catalog based-scan was in running state.

Then we tried below steps :
log on to the machine as root or equivalent and stop the besclient

service besclient stop

Then check if any wscan processes are running, and kill them if they are
wscanhw
wscansw
wscanfs

Delete the following folders if they exist:
/opt/tivoli/cit
/etc/cit
/var/opt/BESClient/LMT/CIT/

Start the bes client
service besclient start

Reinstall ILMT scanner and initiate software scan

Post running this the catalog based-scan is still getting stuck on running state and showing below status.

Clock Out of Sync - False
Is archive size exceeded? - False
Low on Disk Space - False
Status of Catalog-based Scan - Running
Status of Resource Utilization Scan - No information
Status of Scan for Package Data - OK
Status of Scan for Software Identification Tag Files - No information
Time of Last Scan Attempt - 2023-09-14 08:39:55 UTC
Time of Last Successful Catalog-based Scan - No information
Time of Last Successful Resource Utilization Scan - No information
Time of Last Successful Scan for Package Data - 2023-09-14 08:39:57 UTC
Time of Last Successful Scan for Software Identification Tag Files - No information
Total Time of Last Successful Software Scan - No information

How big are the filesystems you are seeing this on? I have seen this happen on servers with enormous filesystems to take days and even weeks… Welcome to open support case on it but the only suggestions you would get see if you can exclude directories. Not a bad one because it is something you ought to be doing (IF you have any large filesystems/directories that you know for a fact do not contain software install binaries like backup, Database/Applicaiton data, etc - exclude those, so scans do not need to bother with them) but it is not always possible (if you happen to have a drives with mixed data & binaries at the same location…