Project and Portfolio Management Practitioners Forum
cancel

Custom report failing after upgrade to PPM 9.14 to 9.31

SOLVED
Go to solution
Highlighted
shijub
Respected Contributor.

Custom report failing after upgrade to PPM 9.14 to 9.31

Hi ALl,

 

We have receiving the below error when we run one of the custom report.

SQL query is running successfully from Sql developer.

Please find error log

/opt/oracle/product/client_11g64/bin/sqlplus ppm_user/#!#*****#!#@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=XXXX)(PORT=30650)))(CONNECT_DATA=(SERVICE_NAME=XXX))) @./scripts/ABC/SPE_FIscal_Year_COMP.sql  '/opt/ppmdev/ppm/reports/' 'rep_117605' '1' '2015'
���������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������
exit code = 1
Errors occurred during command execution

 

One of the custom reports are running fine as required, but few of them fails, giving similar error.

This is failing after upgrading PPM from 9.14 to 9.31.

 

Thanks in advance.

2 REPLIES
alex-h
Super Contributor.

Re: Custom report failing after upgrade to PPM 9.14 to 9.31

Hello,

 

PPM 9.2 and 9.31 integrates a change in reports for multivaluated tokens.

#@# separator has been replaced by comma.

 

PPM 9.31 patch 2 and PPM 9.32 use again #@# as a separator for tokens.

 

 

So double-check report type parameters, maybe one of them is multivaluated.

 

Regards,

Alex-H

shijub
Respected Contributor.
Solution

Re: Custom report failing after upgrade to PPM 9.14 to 9.31

we had the db_util package for sending mail from database, ppm_user did not have the required access to execute, hence the report was failing.