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 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 Dimensions RM how to collect system and DB information (RM 10.1.4, RM 10.1.2, 2009 R1.01, 2009 R2)
System Information Under the FILE menu please select EXPORT For the file name please user the <case number>_SysInfo.txt
CMS-XML Dim: How to install server only, with an existing schema, on UNIX/Linux
DM_DEFAULT_DBMS ORACLE $DM_ROOT/ -- set ORACLE_HOME to proper Oracle home folder, and add LD_LIBRARY_PATH, pointing to lib folders for both Dimensions CM and Oracle, as in the following example: ORACLE_HOME=/opt/serena/oracle/11_2; export ORACLE_HOME
PDF TeamTrack Database Schema
This table records information about objects that are truly deleted from the database. This data is exported in the instance.xml file of the Application Definition package so that the intentionally deleted objects will not be unintentionally recreated upon import.
CMS-XML Important information if exporting data from Oracle 11GR2
The above problem does NOT affect EXPDP (the Data Pump version of EXP), which will export empty tables. So another workaround would be to use EXPDP/IMPDP when moving schemas .
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 server.log shows error "PLS-553 Character set name is not recognized" When starting jboss and AE won't connect.
"ORA-06552 PL/SQL Compilation unit analysis terminated" "Character set name is not recognized" This error was seen when an Oracle db was exported from an Oracle 10 db and imported to Oracle 11g
CMS-XML 10.1.x / Oracle 10g : why the Dimensions oracle instance is created with remote_os_authent set to true ?
In general, some of the "DBA" functions use the REMOTE_OS_AUTHENT. Therefore, if this is set to false, or otherwise disabled, operations such as creating a new base database , deleting a base database schema , creating a reporting user and exporting a control plan export file may not work correctly. In general, all of end-user functions should function correctly such as check-in, check-out, get copy, create requests, relating objects, creating baselines, creating releases and working in projects.
CMS-XML Dim2009R1: Addressing General Oracle Performance Problems for a Dimensions database
a) Perform an export of the base database with rows=n. This will send all the schema information, such as tables, columns, indexes, constraints, views, etc. and none of the customer data. The following commands may be used:
CMS-XML Dim2009R1: How to Recreate Missing Indexes in Dimensions database
exp < basedb >/<password>@<oracle-sid> file=Dim2009R2_schema.exp rows=n grants=n
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs