| |
Results |
|
KM-Dim9: There is no way to change / modify revision number on an existing item revision. This value is present in multiple tables within the schema, and Support does not have a script to update this value, nor do we have a schema description that will allow
|
There is no way to change / modify revision number on an existing item revision. This value is present in multiple tables within the schema, and Support does not have a script to update this value, nor do we have a schema description that will allow us to create such a script. Unfortunately the only option you have is to check out problem description and then check it back in using a different revision number (or use the UI command), then you can delete the original revision .
|
|
|
|
After upgrade Composer fails to validate if table database name >24 characters. Worked in previous version.
|
Composer will not fail to validate if there is a table db name with length of greater than 24 characters, but it will not allow users to type in new table db names greater than 24 characters.
|
|
|
|
KM-Dim8: How to check that item library files exist for each item revision in the database.
|
Run the following SQL to create a UNIX/Linux shell script that confirms the existence of the appropriate file in the item library: sqlplus < basedb >/<password>@<dsn> SQL> set heading off
|
|
|
|
Checked-out revisions are not visible after upgrade to 14.1.0.4
|
If revisions are checked out before base database is upgrade from pre 14.1 version to 14.1.0.x, after upgrade checked out revision is not visible in Web Client when Latest Revision filter is enabled.
|
|
|
|
KM-Dim10: Reported Defect DEF75604: check-out - produces a branch revision on a Workset that has no branch
|
Then from sqlplus as the base database user, execute the script sql-final-check.sql (parameters are case sensitive):
|
|
|
|
RM: Issues if Configure Database Schema is not enabled during the upgrade from releases earlier than RM 09 R1 or for a new installation.
|
The database schema in RM 09 R1 has been updated. Please make sure to include the "Configure Database Schema " option during the upgrade to RM 09 R1 from earlier versions or for a new installation.
|
|
|
|
Dim12: Install: There were errors creating the PCMS_SYS schema
|
11gR2 Oracle Case Sensitivity To ensure correct functioning of Dimensions CM for the 11gR2 versions of the Serena-Supplied Runtime RDBMS, case-sensitivity (introduced in Oracle 11gR2 by default) has been disabled, that is, the runtime is caseinsensitive. +++
|
|
|
ChangeMan ZMF 7.1.3 Migration Guide Version 6.1.x to 7.1.3
|
CMN$$CDB Add Routine to record and copy DB2 DBRM to a DBRM staging library CMN$$CND Add Routine to check for COND CODE failure when some steps use COND=(8,LT) CMN$$COE Add Routine to compile Enterprise COBOL source code, including CICS and DB2 CMN$$ DB 0 Add Routine to set up Java debug and other settings CMN$$ DB 1 Add Routine to post process SQLJ output and produce DBRMs CMN$$F16 Add Routine to FTP data to ...
|
|
|
|
PVCS Tracker Database Schema Contents
|
The first three operations, other than creating association records and module records, will also perform actual Version Manager operations. The last command, module management, lets users directly manipulate the association records without the use of Version Manager. The users can type in the check in revision , check out revision , and change text without actually affecting their archives.
|
|
|
|
Dim RM - Class Definition was unable to validate the user name.Logon failure
|
Go RM-Manage > Login using Project Administrator > Right the Project > Define Project Schema .
|
|
|
