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  
Pages [Next]
CMS-XML Dim cm 14.4 with Postgres database : crdb with Oracle export file fails with this error : insert or update on table "cm_promote_history" violates foreign key constraint "ch_promote_history_k2"
With Dimensions 14.4 server installed with a Postgres database, creation of a base database from an Oracle export file fails as follow : Importing table "CM_PROMOTE_HISTORY" ... DBI4404527E DBIO: Database I/O error occurred
CMS-XML Dim14: Upgrade: DBA3200309E Internal error: Bad input creating project history file arc: aa/bb/cc
Please provide a screenshot of the complete error message and a database export of your basedatabase or a database export of the xii_psh table to Serena Support for additional review.
CMS-XML TRK: Error: SQL State=S1000 [MERANT][ODBC Sybase driver][SQL Server]The 'CREATE TABLE' command is not allowed within a multi-statement transaction in the 'projectname'> database.
As stated in the Tracker 7.1 ReadMe file :
CMS-XML Error: #1155 [Intersolv][ODBC dBase Driver] Cannot open file r:/project/tracker/db/datactr/trkscrsl.dbf
User didn't have full rights in the project database directory, in this case they were missing modify rights (with dBase if you don't have modify rights when dBase tries to modify a table , dBase will delete the table ) Solution:
CMS-XML MCLG: "Check out failed, Unable to check out asset. SQLException:ASA Error -193: Primary key for table 'AssetVersion' is not unique SQLState: 23W01 errorCode: 2601" when trying to check out an asset.
This solution may require sql to be run that requires you to delete data. It's recommended that a database backup be done before deleting any data via sql.
CMS-XML Deleting a contact from the SBM Administrator tool in the Contacts Auxiliary table you may get the following error in the UI and the contact doesn't get deleted. "An exception occurred while attempting to fetch a record count or a record integer value from the database"
Or Exception occurred in file : 'AppRecordList.cpp', line 359.
CMS-XML Inconsistent baseline data in database table
When user is trying to revise a baseline, Dimensions returns an error similar to the following: Revise Baseline - PCM0005301E Error : Inconsistent baseline data in database tables , Item “ file 1#rev1” (uid=4241480), [2]. Aborting baseline creation.
CMS-XML Dim9: Creating revised baseline results in Error: Baseline path required for is already in use by
Steps are as follows: 1. Make sure base database , or at least the item_sets table , is backed up. 2. Logon to SQLPlus as basedb.
CMS-XML Dim12: Upgrade: SQL Server: [Microsoft][ODBC SQL Server Driver][SQL Server]The INSERT statement conflicted with the FOREIGN KEY constraint "ws_ide_projects_fk3". The conflict occurred in database "Dimensions", table "CM_TYPCIAL.WS_CATALOGUE", column 'obj_uid'.
Error detected in C:\Program Files \Serena\Dimensions 12.2\CM\dbms\upgrade\upgradedb_1221.sql, line 405
CMS-XML KM-Dim7: Oracle Bug 90081 may cause Dr. Watson application errors or core dumps when importing a full system export of an Oracle 8.1.5 database.
You attempt to IMPORT using FROMUSER and TOUSER clauses to import a specific user from the export file. The precomputed statistics appear in the export file in a table which is in another schema to that being imported and that table appears in the export file BEFORE the user/ table you wish to import. An 8.1.5.X version of import is being used.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs