The Oracle Management Option Service and/or Oracle Verified Solution Service logs contain the following warning message, possibly multiple times:
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1.
This message indicates that the application attempted to collect JSON data from the ClientStorageData table in the inventory database, but the data chunk was too large to handle.
To resolve this issue, you can alter the chunk size settings in the configuration files to collect fewer computerids each time. First identify which setting to change, then follow the steps to solve.
Identify the correct setting to change
To determine which chunk size setting needs to be adjusted, analyze the logs to see which script caused the error:
The Snow Oracle Management Option Service (OMO) will process the various script outputs in the following order:
- ScriptName: SnowMiddlewareScanner
- ScriptName: SnowMiddlewareScannerV2
- ScriptName: SnowInventoryOracleScanner (Options usage interpretation)
- ScriptName: SnowInventoryJavaScanner
The Snow License Manager Oracle Verified Solution Service (OVS) will process the various script outputs in the following order:
- ScriptName: vsphere-ovs
- ScriptName: SiosOvs
- ScriptName: SnowOracleHardwareScanner
- ScriptName: SiomsOvs
Below are some examples to help you understand where the error is occurring and which setting to change depending on which script failed.
Error examples
Snow Oracle Management Option Service (OMO)
Middleware
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1, ScriptName: SnowMiddlewareScannerV2, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_Site, FromDate: 2024/09/02 12:00:00 AM, ChunkSize: 50
To resolve these types of errors, lower the MiddlewareChunkSize.
Options Usage Interpretation
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1, ScriptName: SnowInventoryOracleScanner, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_Site, FromDate: 2024-09-09 00:00:00, ChunkSize: 50
To resolve these types of warnings, lower the UsageInterpretationChunkSize.
Java
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1, ScriptName: SnowInventoryJavaScanner, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_Site, FromDate: 2024/09/02 12:00:00 AM, ChunkSize: 50
To resolve these types of errors, lower the JavaChunkSize.
Snow License Manager Oracle Verified Solution Service (OVS)
OvsDatabase
(Covers multiple scripts)
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1, ScriptName: vsphere-ovs, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_Site, FromDate: 30/05/2024 00:00:00, ChunkSize: 50
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1, ScriptName: SiosOvs, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_Site, FromDate: 08.10.2024 00:00:00, ChunkSize: 50
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=1, ScriptName: SnowOracleHardwareScanner, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_site, FromDate: 09.10.2024 00:00:00, ChunkSize: 50
To resolve these types of warnings, lower the OvsDatabaseChunkSize.
OvsMiddleware
[WRN] (SnowSoftware.OracleManagementOption.Services.Data.ApiService) GetClientStorageDataList throw (Chunk size too large) exception for TenantId=2, ScriptName: SiomsOvs, ServerAddress: https://invsrv.robslab.local, InventorySiteName: Rob_Site, FromDate: 04.10.2024 00:00:00, ChunkSize: 50
To resolve these types of errors, lower the OvsMiddlewareChunkSize
Performance considerations
Lowering the chunk size means fewer computerids will be processed in one go, potentially leading to longer run times for the service. Be mindful of this trade-off.
Steps to solve
- Identify the Service: Determine whether the issue is with the Snow Oracle Management Option (OMO) service or the Snow License Manager Oracle Verified Solution (OVS) service.
- Locate the Configuration File:
- For OMO service: C:\Program Files\Snow Software\Snow License Manager\Services\OracleManagementOption\appsettings.json
- For OVS service: C:\Program Files\Snow Software\Snow License Manager\Services\OracleVerifiedSolution\appsettings.json
- Modify the Chunk Size:
- Open the relevant configuration file using a text editor like Notepad++.
- In the UserConfiguration section, update the chunk size settings:
- For OMO service: MiddlewareChunkSize, UsageInterpretationChunkSize, JavaChunkSize
- For OVS service: OvsDatabaseChunkSize, OvsMiddlewareChunkSize
Example:
"UserConfiguration": {
"ConnectionTimeout": "00:02:00",
"MiddlewareChunkSize": 30,
"DataUpdateJobName": "License Manager Data Update",
"UseMiddlewareOptimisation": false
}
Note: When inserting extra lines in this configuration, the last setting in this section must not end with a comma; otherwise, the service will not start. All other settings must also end with a comma.
- Restart the Service: After making the changes, restart the relevant service (OMO or OVS).
Additional tips
If you encounter a SystemOutOfMemoryException, consider using the MaxPastDaysFetchRawData setting introduced in SLM 9.33 to limit the number of days the service will try to catch up on.
The application generates a URL to request data from the inventory server, splitting it into chunks to manage large amounts of data. If there are many computers to process with high computerids, the URL can become too long and break the API.
Related Articles
"Long running operation was cancelled" appears in the Oracle Order Management option service log 57Number of Views "Error 0xE050019D: 413 Request Entity Too Large" in uploader log 20Number of Views Why the Oracle Instance value appear as Oracle DB product name or Oracle DB Option name 12Number of Views Event ID 10036 appears in the Windows System log of the Commander application server 9Number of Views All Oracle scanners fail and report “invalid jar entry” in the log 94Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago