Analytical Object Build Error
Case Number: 15498260, 15502224
Problem
Sometimes an analytical object build error occurs after upgrading Servigistics. This can happen when building cubes for the Excess Analysis dashboard and the Vendor Performance Management dashboard.
Cause
This occurs when there is an analytical object build dependency on the MANUAL SYSDATE.
Workaround
For customers using the 2.0.0.1 release, the queries can be manually modified. Use these instructions to make the necessary changes:
1. Create a backup of the existing queries.
2. Edit these queries:
◦ QO_SPM_ExcessAnalysis — requires changes in two places
◦ QO_SPM_VendorPerformanceManagement — requires a change in one place
3. Replace this text:
<@%
if(params("PO_dbType") != null && params("PO_dbType").getValue() == "ORACLE") {
return "(select COALESCE( mansysdate, CURRENT_DATE ) from ipcs_mansysdate)";
} else {
return "(select COALESCE( mansysdate, getdate() ) from ipcs_mansysdate)";
}
%@>
with this text:
<@%
if(params("PO_dbType") != null && params("PO_dbType").getValue() == "ORACLE") {
return "(SELECT CASE WHEN EXISTS(SELECT 1 FROM IPCS_MANSYSDATE) then
(SELECT mansysdate FROM IPCS_MANSYSDATE)
ELSE(SELECT current_date from dual)END AS mansysdate from dual)";
} else {
return "(SELECT CASE WHEN EXISTS(SELECT 1 FROM IPCS_MANSYSDATE)
then (SELECT mansysdate FROM IPCS_MANSYSDATE)
ELSE (SELECT cast(getdate() as date))END AS mansysdate)" ;
}
%@>
4. Save the changes and build the analytical objects.