My activities

How to Restore Production Data into Another Environment?

The following procedure will provide steps to copy the database and associated files from one instance to another. The host and target instance should be on the same version of RiskVision for the restoration to be successful. Contact the product support team if the host and target systems are on different versions for RiskVision.

  1. Consider deactivating the Notification Sender job to prevent unwanted email from the Dev/QA server. Once the backup is complete, these may be re-activated.
  2. Verify all servers are running in the same version down to the hotfix level.
  3. DBA takes a recent database backup of the database using the Oracle Datapump tool.
  4. Copy this file to the datapump directory of the target database server.
  5. Stop all the RiskVision services, inclusive of Tomcat, Apache, Jasper Reports and all the connectors on the application server of the target instance.
  6. DBA to open a command prompt on the target database server and log in to a SQL*PLUS session as the system user account.
  7. Drop the current schema owner, for example: Drop user <schema_owner> cascade
  8. Have the DBA import the production database created in step 1 using the Datapump tool
  9. The following stored procedures should be executed as the Schema_Owner whenever there is a manual import of RV dump. exec SP_REFRESH_MVS; exec SP_CORRECT_SEQUENCE;
  10. Copy relevant files from the host application server to target system Agiliance_Home\config replace the agiliance.properties file as well as any file that ends with a '.xml' extension Agiliance_Home\data, replace all folders and files
  11. Restart the RiskVision services that were stopped in step 3. After several minutes, you should be able to login to RiskVision.

Optional: The following steps will help restore reports from production into the second environment

  1. Install Jasper Reports Server on the target environment if not already installed. Refer to the Installation and Configuration Guide for guidance
  2. Open a command prompt on the server that contains the production instance and navigate to <JASPER_HOME>\buildomatic
  3. Create an export file containing all production reports: Js-export --everything --output-zip productionReports.zip
  4. Copy file "productionReports.zip" created in step 13 to any folder on the target server
  5. Open a command prompt on the server that contains the target instance and navigate to <JASPER_HOME>\buildomatic
  6. Modify then run the following command which will import the Jasper report contained in file productionReports.zip. Js-import? input-zip <folder_location>\repository.zip (replace <folder_location> with the actual location of the file you are importing)

For example: Js-import ?input-zip d:\server\backup\repository.zip

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk