I’m just cleaning up some old files here and came across a post from quite some time ago that never got published. Whoops. This was before I officially released the Rejected Record Summary Java routine for analyzing/summarizing a Hyperion data load rejected record file.
So imagine row after row of something like the following:
\\ Member Ac.0170001 Not Found In Database 09 0170001 900 11 .00 \\ Member Ac.0170001 Not Found In Database 09 0170001 904 11 .00 \\ Member Ac.0170001 Not Found In Database 09 0170001 905 11 .00 \\ Member Ac.0170001 Not Found In Database 09 0170001 906 11 .00
You could run the following one-liner on it:
grep \\\\ sample1.txt | sed -e 's/\\\\ Member //' -e 's/Not Found In Database//' | uniq -c | sort -nr
And get something like the following:
24 Ac.0453902 24 Ac.0397511 24 Ac.0171026 24 Ac.0170926 24 Ac.0170126 23 Ac.0909100 23 Ac.0901100 23 Ac.0201220 23 Ac.0170326
Now, hopefully you aren’t getting any rejected records (and certainly not this many, but then again, it’s just test data), but no matter what, your Hyperion automation practices should include regularly inspecting your rejected records, if any, and this might help if you happen to work it in to some automation.
This example of course presumes your Hyperion automation server is running Unix command tools, so alternatively you could install Cygwin or something similar on Windows if you script there. And for complete platform independence, check out my Java library!