We found out the scan result was still listing 10 inventory items, instead of 5.
Then, at same project we upload and replace codebase with less inventory, let's say 5 items and run scan again. For example, we create a project and scan codebase which resulted in 10 inventory items.
Summary This article documents the correct procedure for deleting existing inventory from a project and documents the enhancement request raised in SCA-6506 which aims to track changes to project inventory and delete any inventory with no associated files Symptoms We found an issue which is FNCI don't update the database properly when the CodeBase is replaced. Adding a space to the name allows for Oracle to store a blank string rather than a NULL value. Unfortunately the only way to resolve this error on 6.10.3 is to ensure that any empty strings contain a space (such as " ") or by upgrading to 6.11.1. Resolution A check for these null values was added to the logic of release 6.11.1 to ensure this error was rectified. When processed by MySQL and MS SQL these are treated as a blank string but when processed by Oracle these are treated as NULL values. Cause The bug is caused by the way that FlexNet Code Insight requires empty strings (such as "") to be handled.
Caused by: : ORA-01400: cannot insert NULL into ("PALAMIDAADMIN"."PSE_SCANNED_ITEMS"."NAME_"). The scanEngineDetail.log and the catalina.out log will both contain the the following error: 11:05:11,576 ERROR Encountered an exception during scan commit : Could not execute JDBC batch update. Summary This article documents the known bug recorded in PAS-10636 where scan commits will fail with the 'ORA-01400: cannot insert NULL into ("PALAMIDAADMIN"."PSE_SCANNED_ITEMS"."NAME_")' error Symptoms When scanning a workspace the scan will fail to commit to an Oracle database.