The definition for this privilege is added to the database as part of the schema upgrade. If the database schema has not been upgraded to Dimensions 10.1.3 then this error may occur. To correct the problem, please upgrade the schema with the following:
User with Admin privileges also gets this error . Problem happens only with some checked out revisions, user and Admin are able to cancel check out on other items / revisions.
We tried giving this privilege to the user , but then we still cannot switch project. A message is received that the user does not exist - but that message mentions the user without space in the name (for example "SURENDRAK" in above example).
The first thing to consider is whether another person is editing the request. If so, then the user currently editing the request must complete and commit his or her changes to the database before any other users may edit the request. If the person editing the request has left for the day or there system crashed in the middle of a transaction, then an appropriately privileged user (such as tool manager), may cancel the edit.
The error is caused by PCMS_SYS schema not having SELECT privilege on SYS.ALL_USERS The best solution is to grant this privilege to PCMS_SYS and any user that will be used when invoking dmdba It is also possible to invoke dmdba with --noschemacheck as in:
) to SQL*Plus, then run the following statement: grant select on v_$session to pvcstrkusr This statement will provide needed privileges to Tracker, user should be able to login without any problems.
The user specified in the %DM_ROOT%\dfs\deploy_config.dat file MUST have local logon privileges on the server or agent where the dmdeploysrv process is running.
A new user was created using Copy User function and all privileges are set correctly. When user tries to log in, either he could not login or he gets “ User doesn't have sufficient privilege to execute report” error after login.
