Essbase 21c MaxL Load Rejecting All Rows If One Member Is Missing
(Doc ID 2999147.1)
Last updated on JANUARY 23, 2024
Applies to:
Hyperion Essbase - Version 21.5.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 21.5.1.0.0 version, Product Usage
Essbase 21c MaxL load rejecting all rows if one member is missing
When testing MaxL scripts in the new 21c environment. Unexpected results for a MaxL load are experienced, that does not have this issue in 11.2
Background on the MaxL Process:
Part of a MaxL dataload process is to load a native Essbase level 0 export file into an existing application. The export file has one record in it that contains a member that does not exist in the outline, but many other valid records that should load. Based on behavior in 11.2, we would expect that when the file loads into the app in 21c all valid records load without issue and only the one invalid record is kicked out.
Resulting Behavior in 21c Testing:
- If we try to manually load via EAS lite, we see that the data loads as we expect; the invalid record is kicked out and all other rows load properly.
- If we try to load using MaxL, the data does not load as we expect; instead the data load fails and an error message is thrown.
- If we add the missing member to the outline, the MaxL job loads all data without an issue. While this is expected behavior, it does not reflect a real-life scenario where there is a potential missing member in the dataset.
Requested Resolution:
We would like to resolve this issue by having the data load as expected in the event there is a missing member; i.e having any valid records load properly and only kick out the invalid one(s).
Essbase Log Error Message:
[Fri Dec 15 09:55:59 2023]Local/PriorBud/Main/admin/140397549668096/Info(1013160)
Received Command [DataLoad] from user [admin] with data file [XptLvl0.txt]
[Fri Dec 15 09:55:59 2023]Local/PriorBud/Main/admin/140397549668096/Info(1003040)
Parallel dataload enabled: [1] block prepare threads, [1] block write threads.
[Fri Dec 15 09:57:00 2023]Local/PriorBud/Main/admin/140397549668096/Error(1003050)
Data Load Transaction Aborted With Error [1003119]
ERROR
-----------------------
1003050, 1003119
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. From Linux bash command line execute shell script that calls MaxL script
2. MaxL script runs login command
3. MaxL script runs import command, example: import database $1.$2 data from data_file 'filename.txt' on error write to 'logfile.log';
4. MaxL script logs out
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, unable to run script in 21c.
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! |
In this Document
Symptoms |
Changes |
Cause |
Solution |