search cancel

Ad-Hoc Reports error after copying from one environment to another

book

Article ID: 202243

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

End-user sees the error message below:

jasperserver.log:

jsft-non-scheduler-deployment-74db8494b7-tz8gk_cppmrpt1021_nonSchedulerContainer-5827d292cae1e308771fd149a117334bcb54ff05722af404d5fb6a1fbe6f8207-jasperserver.log
group by "DWH_INV_TEAM"."resource_name", ("DWH_INV_PROJECT"."ag_capex_num" || ' - ' || "DWH_INV_INVESTMENT"."investment_name"), "DWH_INV_TASK"."task_name", "DWH_INV_TASK_LN"."cost_type" order by "DWH_INV_TEAM_RESOURCE_NAME", "Concatenate_DWH_INV_PROJECT_AG_CAPEX_NUM_zmz_DWH_INV_INVESTMENT", "DWH_INV_TASK_TASK_NAME", "DWH_INV_TASK_LN_COST_TYPE" limit 200001 at com.jaspersoft.commons.semantic.dsimpl.JRQueryDataSet$JRDataSetIterator.next(JRQueryDataSet.java:431) at com.jaspersoft.commons.datarator.CachedData.fetchData(CachedData.java:213) ... 208 more Caused by: net.sf.jasperreports.engine.JRException: Error executing SQL statement for: null. at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:347) at com.jaspersoft.jasperserver.api.engine.jasperreports.util.JRTimezoneJdbcQueryExecuter.createDatasource(JRTimezoneJdbcQueryExecuter.java:166) at com.jaspersoft.commons.util.JSControlledJdbcQueryExecuter.run(JSControlledJdbcQueryExecuter.java:154) ... 1 more Caused by: org.postgresql.util.PSQLException: ERROR: relation "sc0pg0000pdwh.dwh_inv_investment" does not exist Position: 457 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2468) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2211) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:309) at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:446) at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:370) at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:149) at org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:108) at sun.reflect.GeneratedMethodAccessor192.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.tomcat.jdbc.pool.StatementFacade$StatementProxy.invoke(StatementFacade.java:114) at com.sun.proxy.$Proxy185.executeQuery(Unknown Source) at net.sf.jasperreports.engine.query.JRJdbcQueryExecuter.createDatasource(JRJdbcQueryExecuter.java:310) ... 3 more 

Cause

When moving JasperReports from one server to another, it impacts the domain name. In this example, when running a report, it was going to sc0pg0000pdwh. It was the former environment (before moving it).

Environment

Clarity PPM 15.8.1

Resolution

When moving JasperReports from one server to another, make sure you update the domain schema.

  • Go to Advanced Reporting
  • Go to Manage
  • Click on "Update Domain Schema

Attachments