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 Dim10: Reported Defects DEF112469: Upgrading Dim9 project to Dim10 - import project from Dimensions and synchronize gives error message
The user performed a Dim 9 DBCS baseDB upgrade to Dimensions 10. When the user tried to import the upgraded DBCS files using " Import from Dimensions Repository" from Eclipse, the user receives an error during the import process in Eclipse.
CMS-XML KM-Dim9: Upgrading Dimensions 8 directly to Dimensions 9 database passwords default back to original passwords
If upgrading a Dimensions 8 environment directly to a Dimensions 9 environment (no export/ import utilitties are used) and previously - the passwords for the base databases were changed in Oracle - the upgrade will revert the passwords back to the original passwords - password for a basedb is the same name as the basedb. You will need to change the passwords accordingly as needed.
CMS-XML Dim CM 10: Upgrade from Dimensions 9 to 10 produces error SQL-2270(018725C0) ORA-02270: no matching unique or primary key for this column-list
Dimensions 9 data was imported and the command " upgrade <basedb> /force" was run to upgrade the schema to Dimensions 10. The following error was produced:
CMS-XML KM-Dim9: DIM 9.1.2 after upgrading from 7.2 - all worset filenames are blank in the PC
During the installation of Dim 9.1.0 PC Client, the user is asked if he wants to import the previous settings -All the users have Dimensions 7.2 client installations.
CMS-XML KM-Dim9: Summary of Upgrade Steps for Dimensions from Dimensions 7.x to 9.x
3. Now we can import the file. Here's the command to import:
CMS-XML Dim10: Steps to upgrade to from Dimensions 8 or 9 to Dimensions 10.1.1
grant connect,resource to intermediate; Run this for each basedatabase that you wish to import . Now import each basedatabase from this export using this IMP command:
CMS-XML KM-Dim7: Dimensions 6.0 to 7.0 manual upgrade import stage fails
KM-Dim7: Dimensions 6.0 to 7.0 manual upgrade import stage fails
CMS-XML Custom reports do not run after upgrade to Project Office 4.2
RESOLUTION Reports must be upgraded to Crystal 9 and then imported back in to the product using the upgrade feature of the Report Store.
CMS-XML Mapping the Custom Column Parameters to an Auxiliary Table (if upgrading from RLC 6.0 without importing the process app snapshots)
This article is for users upgrading from Release Control 6.0 who do not want to deploy the new process apps or snapshots. It explains how to use an auxiliary table to set your custom columns in the Release Control Request and Deployment Unit widgets. If you are using the applications installed with Release Control 6.0.1 or above, the feature described here has already been implemented.
CMS-XML Upgrading from old version to SBM 10.1.5+. Configurator does not offer Config snapshot import during wizard mode.
Upgrading from old version to SBM 10.1.5+. Configurator does not offer Config snapshot import during wizard mode.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions RM: Importing Requirements
This demonstration show you how to import requirements from CSV, Microsoft Word, and Microsoft Excel files to Dimensions RM.

Additional Assistance

  • Submit a Case Online
  • FAQs