| |
Results |
|
Potential file corruption when File Server is used by Version Manager releases prior to VM 8.1.2.2
|
... project or project database no longer loads ... ... be corrected by restoring the affected files ... ... accessing your Project Databases (PDBs) ... You could place the directives above into their own Configuration File (e.g. "VersionCheck.cfg") and then just reference that file in the first line of each of your Project Database Configuration Files using: ... The advantage of such a solution is that you can then easily change the minimum required VM release for all Project Databases at a later point, simply by updating the file "VersionCheck.cfg".
|
|
|
|
Important Dimensions Database Health Check for Oracle Users Regarding Sequence Spacing
|
Important Dimensions Database Health Check for Oracle Users Regarding Sequence Spacing
|
|
|
|
ZMF 5.6.x: Potential for incomplete restore when running CMNBKRST with recovery records.
|
ZMF 5.6.x: Potential for incomplete restore when running CMNBKRST with recovery records.
|
|
|
|
MCLG 4.0: Databases need to be rebuilt using Sybase 8.0.2 (Windows Only)
|
MCLG 4.0: Databases need to be rebuilt using Sybase 8.0.2 (Windows Only)
|
|
|
|
Using Java Plug-in 1.6.0 Update 10 (1.6.0_10) or newer with Version Manager releases prior to VM 8.2 can corrupt your project database
|
P2470 , or upgrade to VM 8.2 or newer. Users of older VM releases should cease using all versions of the Java 1.6 Plug-in to avoid (further) database corruption, and upgrade their Version Manager release to VM 8.2 as soon as possible.
|
|
|
|
Scripts may get truncated on upgrade from TT 6.6.1 to SBM 2.03, 2.04 or 2.05
|
If you upgrade your database from TeamTrack 6.6.1 to Serena Business Mashups 2.03, 2.04 or 2.05 then some of your TeamScripts may get truncated. Please see the solution S136370 for details on how to prevent this issue - Solution S134370
|
|
|
|
After upgrade to TeamTrack 6.6.1.17 or TeamTrack 6.6.1.18, some attachments may not be accessible on items.
|
In certain circumstances, items stored in the database may not have the correct file size recorded in the TS_BLOBS table. This SQL will identify any attachments with this issue. We will be supplying an update statement to fix the issues very soon.
|
|
|
|
ALERT - possible Oracle data loss if upgrading from TeamTrack directly to SBM 2008 2.03, 2.04, 2.05 or 2009 R1
|
(a) Is your TeamTrack database on Oracle? (b) Are you planning on upgrading from TeamTrack 6.6.1 to Serena Business Mashups 2008 2.03, 2.04, 2.05 or 2009 R1 If both of the above are true
|
|
|
|
TTS License - "Init Extension Failed….. Failed to obtain a TTS license" - 63016
|
And (2) You have based your TeamTrack solution on the Sample database that comes with TeamTrack, or are using the “Support Center Solution” without purchasing a license. NEXT STEPS TO THE PERMANENT SOLUTION:
|
|
|
|
MCLG: Getting Deploy Agent ready for the new USA 2007 Daylight Saving Time rules
|
There may also be operating system patches that need to be applied to the Deploy Agent server. Check with the appropriate vendors for details. Also, if the Deploy Agent is used for database deploys, make sure the appropriate operating system patches are also applied to the database server.
|
|
|
