Summary
This article covers the issue where you get an error stating that the /LICMAN/BSENGI table is missing / not available and this causes the SAPReader to fail
Symptoms
When the SAPReader executes, you may get an error similar to:
Line 329: 2015-05-11 13:53:46,756 [SAPRFC.SAPRFC |KPS/00/100] [INFO ] Reading table '/LICMAN/BSENGI' row 0 to 20000...
Line 330: 2015-05-11 13:53:46,787 [SAPRFC.SAPRFC |KPS/00/100] [INFO ] Invoke failure 'TABLE_NOT_AVAILABLE'. Retry!
Line 331: 2015-05-11 13:53:46,787 [SAPRFC.SAPRFC |KPS/00/100] [INFO ] Reading table '/LICMAN/BSENGI' row 0 to 20000...
Line 332: 2015-05-11 13:53:47,256 [SAPRFC.SAPRFC |KPS/00/100] [INFO ] Invoke failure 'Invalid Delta Manager object ID (3 <=> 1)'. Retry!
Line 333: 2015-05-11 13:53:47,256 [SAPRFC.SAPRFC |KPS/00/100] [INFO ] Reading table '/LICMAN/BSENGI' row 0 to 20000...
Line 334: 2015-05-11 13:53:47,272 [SAPRFC.SAPRFC |KPS/00/100] [ERROR] Invoke failure 'TABLE_NOT_AVAILABLE'. Abort...
Line 335: 2015-05-11 13:53:47,272 [SAPReader.SAPReader |KPS/00/100] [ERROR] Error gathering SAP inventory.
Cause
BSENGI is a table installed as part of the satellite transport and contains the package measurement results. The satellite transport is only needed on the CUA master system where CUA functionality is required. If the satellite is not installed on it, then the CUA functionality is not used and SAPReader should still work.
When the transport has been installed, before the SAPReader tires to query a table, it first checks to see if table and columns it wants to query exists. This is done by querying the table DD03L which contains the schema content of the database, this error message suggests that BSENGI doesn't exist in DD03L but is expected.
This can often happen if the satellite has not been installed / imported correctly as it will not then have all the access, files and schema it needs.
You can confirm this by running the following on the SAP system where the error is occurring:
SELECT * from DD03L WHERE TABNAME='/LICMAN/BSENGI'
This will confirm whether the BSENGI table does actually exist or whether there are any issues reading the DD03L schema.
Resolution
If the query on
DD03L was successful but returned 0 results, this suggests an incorrect installation of the satellite transport, here you can either:
- Install the Satellite transport correctly as per the FNM_SAP_InstallationGuide pdf
- Fully uninstall the transport using the 4_Deletion transports as per the same Installation guide.
Either of these should then resolve the issue.