The document discusses several database cleaning commands in Synergy:
1) The collapse command deletes object versions and adjusts history links to clean up unused objects.
2) The clean cache command removes archived source files from the cache directory to free up space.
3) The Save Offline and Delete (SOAD) command saves unwanted objects offline in a DCM package before deleting them from the database.
4) Old baselines and working projects can also be deleted to further clean the database.
8. Database Structure bin cache archive st_root pt lib guild include bitmaps db dcm etc Synergy Database bin - Model scripts and executables not used on the Windows platform. db - Information about the database, in particular, the parameters and the RDBMS database name. dcm - Information for DCM. include - ACCENT model include files for this database and ObjectMake defaults. lib - ACCENT model libraries for this database. In addition, initialization files, help files, triggers, and migrate rules are stored in the lib directory. pt - Contains parameter files used by Telelogic Synergy and Change. st_roo t - Synergy storage root, used to store source files, product files (such as executables, object files and libraries) and archived sources
A conflict, as defined by SYNERGY/CM, is a potential configuration problem within a project. SYNERGY/CM considers source object versions and their associated tasks together. By using this relationship and your project’s update properties, SYNERGY/CM is able to show you potential problems within your project. Detecting and resolving conflicts immediately following a update helps you avoid potential problems with your build before you actually run it! NOTE It is important to do Detect Membership Conflicts immediately following update to ensure the conflict output is consistent. Don’t worry about the details of how to actually detect and resolve conflicts here. You will get to see that elsewhere in this training class. Remember, this is just one of the steps in the build cycle.
A conflict, as defined by SYNERGY/CM, is a potential configuration problem within a project. SYNERGY/CM considers source object versions and their associated tasks together. By using this relationship and your project’s update properties, SYNERGY/CM is able to show you potential problems within your project. Detecting and resolving conflicts immediately following a update helps you avoid potential problems with your build before you actually run it! NOTE It is important to do Detect Membership Conflicts immediately following update to ensure the conflict output is consistent. Don’t worry about the details of how to actually detect and resolve conflicts here. You will get to see that elsewhere in this training class. Remember, this is just one of the steps in the build cycle.
A conflict, as defined by SYNERGY/CM, is a potential configuration problem within a project. SYNERGY/CM considers source object versions and their associated tasks together. By using this relationship and your project’s update properties, SYNERGY/CM is able to show you potential problems within your project. Detecting and resolving conflicts immediately following a update helps you avoid potential problems with your build before you actually run it! NOTE It is important to do Detect Membership Conflicts immediately following update to ensure the conflict output is consistent. Don’t worry about the details of how to actually detect and resolve conflicts here. You will get to see that elsewhere in this training class. Remember, this is just one of the steps in the build cycle.