Version mismatch between Clarity and Data Warehouse schema
searchcancel
Version mismatch between Clarity and Data Warehouse schema
book
Article ID: 195479
calendar_today
Updated On: 08-29-2024
Products
Clarity PPM On PremiseClarity PPM SaaS
Issue/Introduction
There is a version mismatch between Clarity and Data Warehouse. This may cause issues after/during upgrade or when running Load Data Warehouse jobs
How to rectify a version mismatch for the two databases
Environment
Release : All Supported Clarity releases
Resolution
Confirm the versions do not match:
Run this query on your DWH schema and check the results: select * from cmn_dwh_install_history order by installed_date desc
Compare to the Clarity database with query: select * from cmn_install_history order by installed_date desc
If that the versions do not match, this should be corrected
Correct DWH version mismatch:
Option 1:
Use a blank DWH schema to replace the existing DWH schema
The blank schema is on the Clarity server under $clarity\database\backups
Recreate the DB LINK after restoring it
Option 2:
Take a backup of an existing Data Warehouse that's on same version ( i.e. Prod)
Restore to lower environment DWH by replacing the existing schema
Recreate the DB LINK
After fixing the mismatch:
Run the jobs:
Load Data Warehouse -Full
Load Data Warehouse - Access Rights
Additional Information
If you have a patch applied on Clarity then after restoring the blank DWH database, run the following command on the Clarity application server to have the patch from Clarity apply to Data Warehouse:
admin db dwh-upgrade -Dupgrade.phase=maintenance
If you are on a base version of Clarity and do not have any patches applied then DO NOT run this command