This content has been marked as final. Show 4 replies
Can you share your XML record manipulator where you tag each record with the update action? This would be a place where you would see:
<EXPRNODE NAME="ACTION" VALUE="ADD_OR_REPLACE"/>
The missing piece might be: <EXPRNODE NAME="DIM_ACTION" VALUE="ADD"/>
The latest documentation has a good, dedicated partial update guide.
[MDEX 6.3.0 Partial Update Guide|http://docs.oracle.com/cd/E35825_01/MDEX.630/pdf/PartialUpdatesGuide.pdf]
Check the dimension server in your partial pipeline is added as a source to the XML manipulator. If you do any dimension-specific operations, for example:1 person found this helpful
<EXPRNODE NAME="DIM_ACTION" VALUE="ADD"/>
<EXPRNODE NAME="DIMENSION_ID" VALUE="8000"/>
... the dimension server component needs to be an explicit source to the manipulator (as well as to the property mapper and the update adapter).
This error means that you ran forge at one point but didn't apply it all the way to the dgraph. You have a dimval id in your state file that the dgraph doesn't have. To fix it, the easiest way is just to run a baseline again.
Hello Old Endeca Friends, I'm bringing this item back to life.
I have this same issue with MDEX 6.4 and PS 6.1.3.
The update manipulator is hooked to the dimension server which I assume is how the dim val gets into the state file to begin with. Why then doesn't the dgraph pick it up?
This is a big headache. Any further insight would be appreciated. "Just run a baseline" is not a good answer, I need to do partials every hour throughout the day.