In my scenario, assigned analytic privileges 'SYS_BI_CP_ALL' to the user resolved this error.
Hope this helps.