Project and Portfolio Management Practitioners Forum
cancel

Error in Meta Layer synchronization report

SOLVED
Go to solution
Highlighted
Sascha_1
Super Contributor.

Error in Meta Layer synchronization report

Hi at all,

 

i try to run the synchronization report for the db rml user.

Before i checked the privileges of the user:

 

PRIVILEGE

----------------------------------------

CREATE TABLE

CREATE SYNONYM

CREATE SESSION

UNLIMITED TABLESPACE

CREATE VIEW

 

But if i run the report, i get the following error:

 

Process Errors and Messages 
 
Seq   Message
1   No views will be generated as no driving contexts were found for the template "{0}".mpkg_ud_context_value.rml 
  
Synchronization Errors 
 
View Name   Status   Error
MWFL_WORKFLOWS   FAILED   "Create or replace view..." statement failed (KNTA-10510)
ORA-01031: insufficient privileges

 

I did not modify the report commands or anything. So i do not understand, why the report fails.

Attached, you will find the report log.

 

Regards,
Sascha

3 REPLIES
Cat_2
Super Contributor.

Re: Error in Meta Layer synchronization report

Nothing valuable to add other than our system does the same thing. I logged in via SQLPlus as the reporting user and ran one of the view creation scripts included in the output and it worked just fine. There must be something else its trying to do that doesn't show in the logs. I looked again at the permissions that should be applied to the RML user account (based on the createRMLUser script) and they are all there.

 

What DB version are you on? We're on Oracle 10.2.0.4 and PPM 8.01

Sascha_1
Super Contributor.

Re: Error in Meta Layer synchronization report

Hi Cat,

 

we are running PPM 8.02 on Oracle release 11.2.0.1.0

It seems, that the report has a bug on version 8.0.

 

We use PPM 7.5 SP7 on another system and the report execution was successfully.

 

Regards,

Sascha

 

Sascha_1
Super Contributor.
Solution

Re: Error in Meta Layer synchronization report

Hello,

 

after creating a support case for this issue, i got a respone from HP support. It is a known error since PPM 8.01 and is tracked via enhancement request:

http://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_QCCR1L25755

 

Regards

Sascha