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 Migrating Tracker Data to SBM
There are two methods for migrating from Tracker to SBM. You can either:
CMS-XML Dim12.2: SVN2DM: After migrating data from Subversion, only the trunk revisions were migrated
Dim12.2: SVN2DM: After migrating data from Subversion, only the trunk revisions were migrated
CMS-XML KM-Dim10: When performing the VM Migration to Dimensions CM, an error of 'Error: You must have the appropriate privilege to run this utility' occurs when migrating data.
KM-Dim10: When performing the VM Migration to Dimensions CM, an error of 'Error: You must have the appropriate privilege to run this utility' occurs when migrating data .
CMS-XML Dim CM 14.4: "Error: Unexpected end of data for COPY command" - generated when migrating a Dimensions schema from Oracle to PostgreSQL
When attempting to migrate a Dimensions schema from Oracle to PostgreSQL the following output was produced during the CRDB operation: Importing table "WSET_LISTS" ... Importing table "WSET_LISTS_LOCK" ...
CMS-XML VM2DM: After performing a migration of data from Version Manager, the history of the migrated items shows the revisions twice.
After performing a VM2DM migration , the migrated files history is showing two revisions of each. In turn, when performing the first checkout of the item, the history shows that the item is checked out twice, again with the same revision. After this initial checkout the history then 'corrects' itself and only shows one revision for subsequenting revisions of the item.
CMS-XML Dim CM: Errors "DBI4404527E DBIO: Database I/O error occurred", "DBI4502580E DBC:-9999-ERROR: out of memory" and "DBI4402010E DBIO: Failed to write data to the large object" migrating schema from Oracle to PostgreSQL
During the import phase of migrating a Dimensions CM schema from Oracle to PostgreSQL the following errors occurred part way through importing the tables: DBI4404527E DBIO: Database I/O error occurred DBI4502580E DBC:-9999-ERROR: out of memory
CMS-XML Actual data needs to migrate correctly when no resource assigned to task
* Check in the task plan. * Note all of the data values for actual in order to verify the mismatch after migrating. 4. Now run the migration tool to migrate to the 2009R1 GA version first.
CMS-XML LISTV or 3.4 with IBM's TDMF (transparent data migration facility) causes user tso session hang
Problem started after installation of a new disk (DS8880) subsystem. TDMF was used to migrate volumes to the new disk subsystem. Option in TDMF was SPIDFENCE which puts the soft volume into soft fence state
CMS-XML KM-Dim9: Data Migration Utility will generate UI statements for uploading items which have existing revisions in Dimensions. All new items will have CI statements generated.
If they are unrelated then you have to migrate into an empty workset anyway. Then you will not have any workset filename conflicts.
CMS-XML DIM9: Data Migration Utility and CM Rules.
DIM9: Data Migration Utility and CM Rules.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs