_InspectorMetadata Schema Loads Zero Records in Incorta

[poojapatel17]

Symptoms

• Table load completes without errors, but the record count remains 0 after the load
• Load status appears as successful despite no data being populated in the target table
• This behavior occurs consistently each time the table is loaded

Diagnosis

• The table load completes successfully in the UI, but 0 records are extracted and loaded for _InspectorMetadata tables
• Inspector logs show the following error:

1192 [main] INFO  com.incorta.inspector.client.net.OfflineGetter - Extracted Tenant Path from internal `.zip / .properties` file is: 
2215 [main] INFO  com.incorta.inspector.client.net.OfflineGetter - Extracted Tenant Path from external `.properties` file is: gs://ic-edion-prod-grium-bucket/Tenants/rose
35141 [main] INFO  com.incorta.inspector.Inspector - Validating Tenant
35141 [main] INFO  com.incorta.inspector.Validation - Getting List of Users
44592 [main] ERROR com.incorta.inspector.Inspector - Java heap space
java.lang.OutOfMemoryError: Java heap space
 at java.util.Arrays.copyOf(Arrays.java:3481) ~[?:?]
 at java.util.ArrayList.grow(ArrayList.java:237) ~[?:?]
 at java.util.ArrayList.addAll(ArrayList.java:678) ~[?:?]
 at com.incorta.inspector.client.net.OfflineGetter.getUsersFromSecurity(OfflineGetter.java:968) ~[inspector.jar:1.0]
 at com.incorta.inspector.client.net.OfflineGetter.getUsers(OfflineGetter.java:991) ~[inspector.jar:1.0]
 at com.incorta.inspector.Validation.initUsers(Validation.java:3191) ~[inspector.jar:1.0]
 at com.incorta.inspector.Validation.validate(Validation.java:3206) ~[inspector.jar:1.0]
 at com.incorta.inspector.Validation.validate(Validation.java:3163) ~[inspector.jar:1.0]
 at com.incorta.inspector.Inspector.createDataValidationReport(Inspector.java:390) ~[inspector.jar:1.0]
 at com.incorta.inspector.Inspector.execute(Inspector.java:272) ~[inspector.jar:1.0]
 at com.incorta.inspector.Inspector.main(Inspector.java:248) ~[inspector.jar:1.0]

• This indicates that the Inspector process runs out of heap memory while processing user and security metadata
• Because the failure happens internally during Inspector execution, the UI still reports the load as Success, even though the metadata extraction is incomplete
• As a result, the _InspectorMetadata schema is created, but no data is populated in its tables

Solution

1. Increase the Inspector memory allocation from 2 GB to 6 GB by updating the following file:

/home/incorta/IncortaAnalytics/cmc/inspector/options.properties

2. Save the file and rerun the Inspector process

3. Verify that the _InspectorMetadata Tables now populate correctly