| |
Results |
|
Log files grow exponentially even when there is no activity in SQL 2000 database
|
SQL 2K server - The log files are growing by 100 mb /hour even when there is no ecm activity taking place. See attachment for the trace file that was requested by R&D and attached by user.
|
|
|
|
PowerBuilder integration
|
Source control systems track and store the history of objects. These tools make it easier to keep track of the changes, how to do recovery, and how to manage multiple developers working on one project.
|
|
|
|
Upgrade fails and results with JavaExceptions
|
java.sql.SQLException: Protocol violation original exception stack trace java.sql.SQLException: Protocol violation
|
|
|
|
AIX Installation Error
|
STACK_TRACE : 11 java.lang.NullPointerException at com.installshield.product.SoftwareObjectUtils.updateKey(SoftwareObjectUtils.java:21)
|
|
|
|
Package installation fails and deletes files when freeze name more than 50 chars
|
The freeze name that ChangeMan automatically creates is a concatenation of several strings: freeze name = package name + target production area name + string pre-install. If this freeze name happens to be more than the 50 character limit set by ChangeMan, then the package installation fails. As a result of this failure, an obscure Java error message is received with a Java stack trace in the package installation history.
|
|
|
|
Server Sizing Guidelines
|
eChange Man keeps track of the on-going changes made to the files it manages in Archives. Since changes are most important in the baseline or production environment eChange Man allows an archive to be defined for each production area. It is through the use of these archives that eChange Man is able to perform required tasks such as Rollback, Check out of previous versions, or to compare previous versions.
|
|
|
