Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML DMCM: Pulse connection failure following manual upgrade to 14.x
After upgrading to Dimensions 14.x from a release prior to 14.1 using the manual DMDBA method, the PULSE user is normally created manually as indicated in the installation documentation, and this user subsequently has database objects created when the first connection is made to Pulse. However, if this is not happening and the objects in the Pulse schema are not created in the database, this indicates that the database.jdbcurl is not set correctly.
CMS-XML SBM: Tomcat will not stay running. Console log gives: Failed upgrading SLA server schema
After an upgrade , Tomcat will start, run for a few seconds, and stop. When looking in the console.log, the following error displays:
CMS-XML Dim12: Upgrade: Database schema update fails: ACL4501561E Error: Could not load library libdbio_srv_odbc.so
The upgrade log files report Dimensions CM DMDBA 12.2.2 Build 9.289 (Production) at 09:50:34 Friday 15 March 2013
CMS-XML Upgrade DB to SBM 10.1.4 from TT 661 on Oracle fails
it is possible that not all scenarios for upgrade of TeamTrack databases to SBM have been covered. While there was a defect fixed in 10.1.4 to handle this, you may still find issues when attempting upgrade of TT 661 databases.
CMS-XML ResMan server schema failed during upgrade of Common Services, but no error was logged during the upgrade
During the upgrade itself, there are no errors logged when the ResMan (Resource Manager), work center or SLS schemas are upgraded. If there are any problems during the upgrade , you will not see the errors until you try to log into work center.
CMS-XML Dim: Upgrade to CM 14.1.0.4 - Baselines and projects in schema fails to upgrade because of path conflicts between directories and directory items
Baselines and projects in schema fails to upgrade because of path conflicts between directories and directory items. Examples of Baselines upgrade Errors DBA3200088E Path conflict: Directory UID 5528454 conflicts with item 'TESTMAN:LIB-5279050.A-DAT' at 'etc/Utilities/TESTMM0001MYFILE/Lib/'.
CMS-XML KM-Dim10: DMDBA upgrade base DB or CRDB gives error ORA-28003: password verification for the specified password failed
When the user tried to run upgrade <basedb> command from DMDBA to upgrade their imported Dimensions 9.1.3 basedb, they receives following errors.. "ORA-28003: password verification for the specified password failed "
CMS-XML DIM CM: Upgrade of BASEDB fails with SQL-1(90018) ORA-00001: unique constraint (BASEDB.VRS_1_AC_PK) violated
Upgrade fails at upgrading vrs_1_arc_changes in $G:$G. DBI0004527E DBIO: Database I/O error occurred SQL-1(90018) ORA-00001: unique constraint (
CMS-XML KM-Dim10: Upgrade from database export fails if build projects not verified
If a Dimensions 9 base database containing build projects is upgraded to Dimensions 10 on a server with only Dimensions 10 binaries (in effect a "clean" migration), running " upgrade all" will fail . Furthermore, the situation is made worse as there are no Dimensions 9 binaries present, and the PBA command cannot be run on the Build Projects. In this situation, there are two approaches to resolve the problem - both are detailed below.
CMS-XML Imported DB with Action on Transition fails in Mashup
Customer is trying to upgrade TT 6.6.1 databases to Mashup, but the resulting Mashup db does not work properly, Actions that work fine before do now fail with this error:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs