Clarity

Hi all. I'm learning new skills today...

We've rolled back our Production transactional database back to our Development environment. I've completed all activities in my old (13.2) rollback procedure. Now it's time for the new stuff.

1) I can't get this to work (14.3 on windows).

- I've successfully generated they new keystore file and properties by executing Admin Jaspersoft generate and copied them to the Jasper Server's <Tomcat>/webapps/reportservice/WEB-INF/config

- I've not had success with Admin content-jaspersoft command. If one simply copies & runs the command as written I get a 'The system cannot find the file specified' error (note: the command as documented is not calling the -fileName switch). Add to this that the command, as documented, doesn't appear to be syntactically correct.

Shouldn't it be something more like Admin content-jaspersoft csk upgrade –userName superuser -password superuser -retryCount 50 -force force

This gives me a username and password are empty error which I disagree with (don't tell anyone I kept the default values from the install )

So this has me stumped.

My second question is from what Nika_Hadzhikidi references here:

"Backup is also needed when you refresh another environment with PPM and DWH, as we recommend refreshing both, however for this purpose you may schedule a separate backup and that's not something that is done on a frequent basis."

Why do I need to roll back my Data Warehouse database to my Dev & Test environments? The Data Warehouse is disposable - we're running a full rebuild every night. I'd actually prefer that first full load just rebuild it from the newly rolled back OLTP database.

Hi Robert,

In 14.3 there are changes to the Jaspersoft commands. The upgrade command does no longer work in the same way and it's used to apply Jaspersoft patches. And you also do not have to "upgrade" or reimport the content anymore.

Please just ensure your keystore is regenerated, then run the commands:

admin jaspersoft syncPPMContext -userName superuser -password superuser

admin content-jaspersoft csk restoreDomains -userName superuser -password superuser

This should resolve the issue. Once you do, please ensure the Report server is Available in CSA and run Create Jaspersoft Users job to ensure it connects fine.

Concerning DWH : We recommend refreshing both due to few reasons, the most important of which is that if you don't refresh DWH, but only PPM on one environment, you risk to run into issues with mismatches in DWH between environments.
You can either use the refresh from Prod to restore to Dev, or use a blank database, both are possible and safe and should not cause an issue.

The impact of using a blank database is that data is not immediately available, and you have to ensure you run the following command on the app server after the database gets restored and configured in CSA:

admin db dwh-upgrade -Dupgrade.phase=maintenance

This command should be used if you have any patches installed. It will basically ensure that any database changes that were applied by the patches will be reapplied on the database level to the new backup.

After you run the command successfully, you will have to run Load Data Warehouse - Full Load and Load Data Warehouse - Access Rights to populate your data.

I hope this helps.

Kind Regards -Nika

Awesome Nika - Thanks. The above commands ran successfully and the Create and Update Jaspsersoft Uses job finished successfully. Let's update or retire TEC1136332. I'd prefer to have operational process documentation like this over in the DocOps.

I don't know why anyone would think they could (or... why would they?) roll back an OLTP database that is out of sync with the patch level that is in a Dev or Test environment. Because of this thread I've recently opened a ticket with my DBA team to stop taking backups of our data warehouse - I'm going to look kind of silly if I ask them for a backup now. I want to ride out the Full Load job and see what happens.

Is there any harrm in running admin db dwh-upgrade -Dupgrade.phase=maintenance even if it's not needed? If it's safe I'd like to add it to my roll back procedures just to ensure coverage.