Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
CMS-XML DIM CM: DBA3203058E "" is not a release baseline
Archive baselines with path conflicts can't be fixed with the UAP .
CMS-XML CM 14.x : invoking vrscli or u141check returns "the procedure entry point ... could not be located in the dynamic link library libvrs10u.dll"
this was due because user didn't install the correct version of uap pack. Dimensions server was in 14.2 and it has been installed uap pack for version instead of uap pack for the 14.2
CMS-XML Dim14.3.3: Upgrade: How to disable the Path Version portion of the upgrade and run at a later time
NOTE: If you are upgrading to Dimensions CM 14.3.2, please contact Support for a possible patch to the UAP which is provided with Dimensions 14.3.2.
CMS-XML Dim CM 14.x: Unique constraint violations on VRS_1_A_F1 and/or VRS_2_P_PK during schema or VRS upgrades
These constraint errors are typically caused by repeated upgrade runs without cleaning up properly. Please make sure that in addition to rolling back (or running the Upgrade Assistance Pack ( UAP ) reset scripts if provided to you by Support) you empty and disable the Oracle recycle bin and empty the DB cache directory (as defined by DB_CACHE_DIR in dm.cfg). If the cache directory contains entries for a previous attempt you will see these errors.
CMS-XML Dim: Upgrade to CM - Baselines and projects in schema fails to upgrade because of path conflicts between directories and directory items
Contact Support regarding the UAP (Upgrade Assistance Pack ( UAP ). You can upgrade the projects and baselines involved by entering the following command in dmdba before the first upgradevrs or upgradebln141 command: dmdba> u141mode strictpaths=off

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs