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 Dim14: When can we drop the XII tables from the database schema?
The XII tables were created during the upgrade process from older versions of Dimensions. These tables contain pre-upgrade data so that we can create and migrate the data into the VRS format. These tables can take up significant space within the database.
CMS-XML Dim CM 14.4: "Error: Unexpected end of data for COPY command" - generated when migrating a Dimensions schema from Oracle to PostgreSQL
The error will be passed to the caller for processing Error: An error occurred while creating the base database - will now delete it. Error: You have not previously connected to "&oldDatabase".
CMS-XML Migrated PE 2.1 databases with a PO Connector set up do not automatically map us
Migrated PE 2.1 databases with a PO Connector set up do not automatically map us
CMS-XML How to migrate WE8ISO8859P1 and US7ASCII databases to UTF8 via the Oracle data pump method
An alternative to using the MIGRATE utility provided with Dimensions is the Data Pump Export and Import functionality provided from Oracle 10g onwards. The migration is valid for any Dimensions release from 10.1.x onwards (i.e. any Dimensions installation that uses Oracle onwards).
CMS-XML DA510: Can version 4.0.1 databases be migrated to version 5.1.0 ?
2) Can the version 4.0.1 dump databases be used by version 5.1.0? If not, is there a way to migrate these dumps over?
CMS-XML MCLG: How to migrate from one database platform to another platform
For example, you may have initially installed Collage to run against the built-in Sybase database and later you decide that you would like to migrate to MSSQL or Oracle. Or, you may have initially decided to install run against MSSQL and would now like to use Oracle. In either case, this document will explain the migration steps.
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 MCLG: When migrate the admin database or project database to Oracle , get error "ORA-06550: line 1, column 7: PLS-00201: identifier 'DBMS_JAVA.GRANT_PERMISSION' must be declared" or "Roll 'Java Admin' does not exist."
Collage requires the Java option in Oracle. This will need to be installed before migrating to Oracle. This is an installation component of Oracle.
CMS-XML Migrating projects already in Version Manager to VS2005 / VM 8.1.3 Rich Integration
13. Go back to Visual Studio and re-open the solution by selecting File | Source Control | Open Project from Source Control. 14 . Select the database , enter the login information, and click <next>. 15. Select a workspace and click <next>.
PDF Serena Tracker to TeamTrack Migration Guide
T TeamScript 84 TeamTrack overview 12 API 84 database , setting up 55 Import Data Wizard introduction 62 introduction for Tracker users 40 item types and Tracker issue types 43 items and Tracker records 43 licenses 53 mass updates 81 primary and auxiliary items 14 , 43 privileges 68 projects 13 reports and Tracker queries 41 Solution Wizard introduction 56 solutions 12 setting up 56 Title field 80 workflows 13 Title field 80 toolkit 83 Tracker elements that cannot be migrated 55 issue relationships 54 issue types and TeamTrack item types 43 permissions 68
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs