RPAS Server: Array Corruptions After Running ScanDomain Utility
(Doc ID 2423878.1)
Last updated on MARCH 08, 2022
Applies to:
Oracle Retail Predictive Application Server - Version 16.0.2 to 16.0.3 [Release 16.0]Oracle Retail Merchandise Financial Planning Enterprise Edition Cloud Service - Version 16.0 to 16.0 [Release 16.0]
Oracle Retail Assortment & Item Planning Enterprise Edition Cloud Service - Version 16.0 to 16.0 [Release 16.0]
Information in this document applies to any platform.
Symptoms
There were many array corruption issues noticed after executing the scanDomain utility. Following are the few of the issues which were identified:
- Deletion of store properties array
- Core dump while scanning/fixing corrupted arrays
- ScanDomain is skipping few of the corrupted arrays
Here are the details on one such case:
When attempting to verify that the dimension space of an array is valid, scanDomain utility checks each dimension contained in the array to see if the dimension is a registered dimension name (i.e. contains in the dim_dim array). If the dimension is a registered dimension, this utility then checks to see if the dimension is contained in a dimension registry. If the dimension is not included in a dimension registry, the utility attempts to update the dimension space forcing that dimension to refer to the dimension registry.
If any domain has registered the dimension 'prop', the store_props arrays will have a single dimension 'prop' contained in the array. So the current scanDomain will attempt to fix these array if it had to scan them. When these array are fixed, the dimension 'prop' of these arrays is updated to use the 'prop' dimension contain in the dimension registry. The array data is map from the old array to the new array. It this case the 'prop' dimension of these arrays does not contain any positions of the 'prop' dimension contained in the dimension registry. The net effect is the content of these arrays is erased. Because of this issue, saved workbooks <workbook>/store.store_props array is also cleared and thereby users are unable to open them. When attempting to open those workbooks, users encounter error:
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |