Absent Member.. rajesh.thanasee Absent Member..
Absent Member..
456 views

Dashboard Issues after DB Refresh

Jump to solution

Hi All,

 

We have performed a DB refresh from PROD to test instance. After starting the test instance, the PPM dashboard behaves in unusual manner.

 

When trying to access any dashboard portlets, it is throwing the below error,

Error:

could not initialize a collection batch: [com.mercury.dashboard.model.portlet.Page.portlets#<491521, 369655809, 369491968, 19070977, 64258062, 369655811, 369655810, 160137216, 369655808>]

 

When trying to search requests, it is showing below error

 

Error

An unknown error has occurred. For more information, please contact your PPM administrator and provide the following GUID number:

GUID=9D21DE88-5C61-18EC-9CCE-F28ADD35667C Generated Time=2015/05/29-17:18:59.343 EDT

 

Any Inptus will be of assistance.

0 Likes
1 Solution

Accepted Solutions
Absent Member.. rajesh.thanasee Absent Member..
Absent Member..

Re: Dashboard Issues after DB Refresh

Jump to solution

Thanks, Scorpex

 

 Dashboards in PPM are dependent on Jar files in the PPM filesystem to be fully functional. The HTML portlets references are stored in jars - utility.portlets. These Portlets relies on utility_portlets.war besides dashboard.war and itg.war. After the DB Refresh we beleive these jar files (responsible for rendering the dashboard pages and searches) weren't synchronizing with the DB and they were failing. In addtion to recompiling the invalid,SQL objects, refreshing the file system of the PPM home directory and rerunning the kConfig/kUpdateHtml.sh restored the syncronization of the dahboard and related components within PPM DB and it's asociated jars .Dashboard and search functionality was restored. it's appears that it's a good practice to refresh the filesystem along with DB refresh for lowertiers to ensure this doesn't break.

4 Replies
Absent Member.. Scorpex Absent Member..
Absent Member..

Re: Dashboard Issues after DB Refresh

Jump to solution

I had one of my users get the batch error with the dashboard when they logged in, the simple solution was that the user had to delete their cache and it worked fine.

 

This might be the case with the machine you are connecting to the test instance it probably has stale cache information.

 

As for the search error do you have the server logs handy?

 

Thanks!

Mig

0 Likes
Absent Member.. rajesh.thanasee Absent Member..
Absent Member..

Re: Dashboard Issues after DB Refresh

Jump to solution

We had tried to refresh the filesystem along with DB once again and things are working now. 

 

Thanks for your inputs.

 

Regards,

Rajesh

0 Likes
Absent Member.. Scorpex Absent Member..
Absent Member..

Re: Dashboard Issues after DB Refresh

Jump to solution

I am glad you are back up and running, if you wouldn't mind could you go ahead and mark this topic as resolved with your solution so that if someone else comes across it they can see the awesome checkmark stating it was resolved?

 

It makes it easier to find for those of us that might experience the same issues.

 

Thanks!

Mig

0 Likes
Absent Member.. rajesh.thanasee Absent Member..
Absent Member..

Re: Dashboard Issues after DB Refresh

Jump to solution

Thanks, Scorpex

 

 Dashboards in PPM are dependent on Jar files in the PPM filesystem to be fully functional. The HTML portlets references are stored in jars - utility.portlets. These Portlets relies on utility_portlets.war besides dashboard.war and itg.war. After the DB Refresh we beleive these jar files (responsible for rendering the dashboard pages and searches) weren't synchronizing with the DB and they were failing. In addtion to recompiling the invalid,SQL objects, refreshing the file system of the PPM home directory and rerunning the kConfig/kUpdateHtml.sh restored the syncronization of the dahboard and related components within PPM DB and it's asociated jars .Dashboard and search functionality was restored. it's appears that it's a good practice to refresh the filesystem along with DB refresh for lowertiers to ensure this doesn't break.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.