Troubleshooting
Problem
After upgrading from 10.2.2 to PA 2.0.x, User unable to edit his node. The user has to release and retake the ownership to perform edits.
Symptom
When executing }tp_workflow__own__responsibility (through the Contributor interface) on an N level node, all DR file entries are removed for a specific node if a separate user has checked out the N level node by requesting ownership of the consolidated parent node prior. This leaves the }tp_application_state cube out of sync with the DR file, resulting in a user needing to release and re-take ownership of a node in order to successfully perform edits.
Cause
When migrating from 10.2.2 to PA 2.0.X, the default (if left blank) Data Reservation Mode is set to REQUIRED. The REQUIRED Data Reservation Mode does not allow for overlapping requests in the DR file, so the first execution of }tp_reserve_slice will fail when called from }tp_workflow__own__responsibility. After this fails, }tp_workflow_util_bounce_nodes will execute and remove the previous user from the DR file, as well as update the application state cube. This will leave the DR file out of sync with the application state cube.
Resolving The Problem
Modifying the data reservation mode to REQUIREDSHARED by editing the cube attributes for the DATARESERVATIONMODE attribute found in the }CubeProperties cube.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD29G","label":"IBM Planning Analytics"},"ARM Category":[{"code":"a8m0z000000cwgYAAQ","label":"How to"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
07 October 2020
UID
ibm16343113