| |
Results |
|
Dim10: ZOS: Temp files are not being cleaned up
|
Dim10: ZOS: Temp files are not being cleaned up
|
|
|
|
SDA: How to remove SDA to perform a clean new install on Windows
|
SDA: How to remove SDA to perform a clean new install on Windows
|
|
|
|
KM-Dim8: Oracle 8.1.7.2 runtime and other components removed when cleanup instructions are followed after upgrade
|
The Dimensions 8 Upgrade contains several optional steps to clean up unused Dimensions 7.2.x.x components after the installation of the new software. These optional steps are not correct as documented and should be ignored.
|
|
|
|
DA: After upgrade to DA 6.3.3 we cannot see options for Execution or Deployment History Cleanup
|
4) In the right-hand, click on the pencil icon to the right of the group you are using, e.g., Admin 5) If it is not already checked, check the box next to " Clean Execution History", then click Save 6) Repeat steps 3 through 5 for Environments and "Web UI".
|
|
|
|
Cleanup obsolete security fields in CMN990 report
|
Cleanup obsolete security fields in CMN990 report
|
|
|
|
Configuring the Execution History Cleanup sweep for hung cleanup requests
|
Configuring the Execution History Cleanup sweep for hung cleanup requests
|
|
|
|
SRA: Rollback configuration - How to remove files as part of rollback
|
In situations where a failure in a process triggers a rollback process and if the deployment area contains files that are not part of the snapshot being used for the rollback, how can we clean up and/or remove the files that do not belong to the snapshot being used for the rollback?
|
|
|
|
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.
|
|
|
|
General maintenance for slow deploys or hanging deploys or take longer than usual in the initializing stage.
|
The following items can be used for general clean up and troubleshooting of deploys hanging or not starting. After using Collage for a while more and more deploy activity is stored in the administration database with not a real automatic way of cleaning it up. Over time you may see deploys hanging, not starting or generally taking a long time in the initializing stage.
|
|
|
|
DIM 12.2: Installation results in Tomcat 5.5 installed instead of Tomcat 6.0
|
The following issue has been seen on several occasions when doing either an upgrade or a clean installation: New 12.2 64 bit install of Server components (on Windows or Solaris) installs only tomcat 5.5 and no 6.0.
|
|
|
