A strange problem has arisen for write enabled cubes.

In the past, specified users have been able to amend cube data
via the client interface. These changes being stored in the specified
writeback table.

However, this now seems to be failing on a regular basis. The user is
being told that they do not have access. Upon checking the write enable
status of the cube in Analysis Manager, I find that it has disabled
itself. The only way to re-enable is to backup the writeback table,
re-enable the write enable option, restore the data and reset access
permissions.

This works well for a few days then again the write enable switches
itself off.

There is no manual switching off occuring and nothing in the logs to
indicate what is causing this.

Any ideas would be appreciated.

Regards
Dazza

We are experimenting with this as well and were told to expect unstability.

We have decided to transport write back data to a partition very often -
perhaps every night - in order to avoid being dependent on the write back
table.

There is an article out there somewhere about this.

But solving your specific problem I don't know what to do.

Perhaps some DSO coding could check this and enable it if it isn't enabled -
but that's beyond my skills...

"Dazza" <post2Group (AT) only (DOT) com> wrote