I set up various reports on DEV stage which are running very well. However in TEST and PRD stage they do not work at all. As far as I can see there’s a problem with the DB in the respective stages. We face the following problems:

• When exporting the RAP, there’s an error in the log files stating "Unable to export table metadata". As an result, while importing the RAP to SI or PRD, there’s no request by PEGA to import a JAR to DB anymore (which was common in earlier deployments)

2017-02-08 09:35:36,157 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ DPFW:01.01.01] (.export.AppBundleArchiveWriter) INFO Proprietary information hidden - Creating Schema Archive: /opt/jboss/jbeap-6/controller/hc/abs_dev_hc_eap_taas2_sl018200/servers/abs_dev_sv_eap_taas2_ts_00/tmp/work/jboss.web/default-host/fermatservice_sach_app_prweb/RuleMgmt/B98B160F94BC7BA11A6D89CB1745E9865/Update0202/schema/Update0202_schema.jar

2017-02-08 09:35:36,511 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ DPFW:01.01.01] (rnal.archive.SchemaArchiveImpl) WARN Proprietary information hidden - Unable to export table metadata for class Azd-FW-DPFW-Data-Audit

2017-02-08 09:35:36,527 [ PegaRULES-Batch-1] [ STANDARD] [ ] [ DPFW:01.01.01] (rnal.archive.SchemaArchiveImpl) WARN Proprietary information hidden - Unable to export table metadata for class Azd-FW-DPFW-Data-Bank

• When I compare the DB tables DEV with TEST and PRD I can see that they are missing columns. FIlling up the DB with the missing columns has not helped to solve the problem.

• When we run a report in SI or PRD we receive that error (see picture 1). This had occurred also in DEV BEFORE I optimized the properties for reporting. If I try to optimize the properties for reporting in SI and PRD, I receive a message that the table or view does not exists (picture 2)

The creation of a new RAP with the wizard hasn't helped, the error on missing data table meta data still remain.

Can anybody help me on that? Thank you!

***Updated by Moderator: Marissa to update categories***