======================================================================
Halcyon PrimeAlert (R) for Sybase Replication Server
Version 2.0.0
Release Notes
======================================================================
Copyright (c) 1998-2003 Halcyon Monitoring Solutions, Inc.
Note: For the latest information on this product, go to the
web site at http://www.HalcyonInc.com
Refer to the README file(s) for all other information.
Versions Documented Below: 2.0.0b 2.0.0a 2.0.0 1.1.1
======================================================================
VERSION/DATE: 2.0.0b/2008-04-11
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun MC 4.0 support.
- Added Solaris 10 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 2.0.0a/2003-07-23
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun MC 3.5 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 2.0.0/2003-02-15
ENHANCEMENTS
----------------------------------------------------------------------
- Support for Solaris 9 (2.9)
- Support for Sun Management Center Performance Reporting Manager.
- Support for Sun Management Center Group Operations.
- Support for Sybase Replication Server 12.5
- Module objects are available in the PrimeAlert Reporter Add/Delete
Rows picklist.
BUG FIXES
----------------------------------------------------------------------
- Module is available in the Module Specification picklist in the
Filters tab of PrimeAlert EventAction.
- Documentation upgrades.
- Alarms messages in some of the tables were not formatted properly.
NOTES
----------------------------------------------------------------------
- Removed Solaris 2.5.1 support.
- Removed Sun Management Center 2.x support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This version of the product contains a new module load parameter
and a new ProcessMonitor module that is not backward compatible. To
successfully upgrade to the current version, the following steps must
be taken:
a) Note the module load parameters of each PrimeAlert for Sybase
Replication Server module loaded in the agent
b) Unload each module from step a)
c) Stop the agent
d) Install the product
e) Execute the HALProcessMonitor-upgrade.sh script provided
e) Start the agent
f) Reload each module that was unloaded in step b) using the module
load parameters determined in step a)
KNOWN PROBLEMS
----------------------------------------------------------------------
- The PrimeAlert for SybaseRS module will go into a DOWN state if the
RSSD transaction logs fills up. This is due to the fact that when
the transaction log is filled, a connection cannot be established.
Workarounds:
1) The RSSD transaction log is currently monitored, to avoid this
problem, try and set the current alarm thresholds so that an alarm
occurs well before the log fills up.
2) The PrimeAlert for Sybase module can be used to also monitor the
RSSD transactions logs. Simply load the Sybase module and specify
the RSSD as one of the databases to be monitored.
======================================================================
VERSION/DATE: 1.1.1/2001-02-21
BUG FIXES:
- Module instance customizations are no longer lost after the module
is reloaded (see KNOWN PROBLEMS section below for exceptions).
- All monitored objects within PrimeAlert for Sybase Replication Server
have a unique instance name now, so PrimeAlert Reporter is optimally
supported.
- When PrimeAlert for Sybase Replication Server is installed on a
Solaris 2.8 host, symbolically linked directories will no longer be
clobbered along the various file installation paths (see additional
item in the KNOWN PROBLEMS section below).
- Fixed a problem that was causing a memory leak in the Sun Management
Center agent process.
- The module can now read tcp-formatted entries in the interfaces file;
formerly, only tli-tcp-formatted entries were supported.
ENHANCEMENTS:
- PrimeAlert for Sybase Replication Server is now interoperable with
Sun Management Center 3.0.
- As documented in the README file for this distribution, all text
documentation files for this distribution are now archived to a
standard location on any installation host.
- This distribution includes a new UNIX uninstallation script; see
the README.install file for details.
- A new table, Disk Partition Summary, exists in the Partitions folder.
This new table summarizes the total, total available, and total
percent used disk space.
KNOWN PROBLEMS:
- For the included module(s), certain tables with more than 50 rows of
data may no longer display properly when using a SunMC 2.1.1 console.
This problem does not occur when using a SunMC 2.1 or 3.x console. If
you are still using the SunMC 2.1.1 console, and you are experiencing
the table display problem, then please contact Halcyon for a patch
(info@HalcyonInc.com).
- User customizations applied to certain pre-configured table rows
may be lost when an instance of PrimeAlert for Sybase Replication
Server is re-loaded (for example, after the SunMC agent process is
re-started):
Case 1 - Folder: Online Engines, Table: Processes
- Delete or modify a pre-configured row in the Processes table; the
row returns to the table (in its original state) after the agent
is re-started.
Case 2 - Folder: Error Logs, Sub-Folders: all, Table: Patterns
- Delete or modify a pre-configured row in the Patterns table; the
row returns to the table (in its original state) after the agent
is re-started.
Suggested Work-Arounds:
- Instead of deleting a pre-configured table row, disable it.
- To modify a pre-configured row (e.g. named 'Insufficient
Resources'), the row should first be disabled; then, a new
(similar) row (e.g. named 'my Insufficient Resources') can be added
and custom configured.
- Assume that a user installs Sun Management Center in the /opt
directory, and then decides to relocate some of the installed
directories (located below /var/opt/SUNWsymon or below
/opt/SUNWsymon) after SunMC is installed. For example, assume that
the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
and then a symbolic link is created to link /opt/SUNWsymon/modules to
/export1/SUNWsymon/modules. In this case, if the current distribution
attempts to install any files in or below the directory
/opt/SUNWsymon/modules, the symbolic link will be replaced by a real
directory. This problem does not occur under Solaris 2.5.1.
- While a route is being created, the RSSD stored procedure shows its
status as 'Route is being created'; however, the Routes table shows
its status as 'Active'.
- The module assumes that both Sybase ASE and Sybase Replication Server
are installed with the same root directory; thus, the module is not
able to monitor the data server process if Sybase ASE is not
installed in the same root directory as Sybase Replication Server.
- When monitoring a remote replication server, and viewing the Error
Logs section of the module, the topology view is blank.
- Some special characters may appear incorrectly in the SunMC console
Help window for some window managers, including Windows NT.
- When a user attempts to view the module help from an NT console, and
a Web browser cannot be found, an error message is logged. The user
should also receive visual feedback indicating how to correct the
problem.
- The authorized user must have a non-blank Sybase password. PrimeAlert
for Sybase Replication Server does not support a blank password for
the authorized user.
UPGRADE STRATEGY:
- A number of *.dat files in /var/opt/SUNWsymon/cfg may be updated so
that they work properly with Sun Management Center 3.0. Prior to the
update, the affected *.dat files will be copied to a backup*
sub-directory in /var/opt/SUNWsymon/cfg.
- If the user is currently using (or plans to use) PrimeAlert Reporter,
and the user wishes to use PrimeAlert Reporter to track objects that
were loaded within a pre-1.1.1 PrimeAlert for Sybase Replication
Server module, then the user may experience minor compatibility
issues when using Reporter to track the pre-1.1.1 SybaseRS objects.
These minor compatibility issues can be resolved by:
- installing PrimeAlert for Sybase Replication Server version 1.1.1
or higher;
- then, restarting the agent on the host where PrimeAlert for
Sybase Replication Server was upgraded;
- then, unloading and reloading all PrimeAlert for Sybase
Replication Server instances on the upgraded agent host. Note
that reloading an instance of PrimeAlert for Sybase Replication
Server will cause all user-entered data to be lost (e.g. custom
alarm limits, pattern-matching regular expressions, and so on).
- This version of PrimeAlert for Sybase Replication Server no longer
supports Sun Enterprise SyMON 2.0.x; only Sun Management Center 2.1
or higher is supported.
- In order to obtain the full benefit of the new features included in
this version of PrimeAlert for Sybase Replication Server, PrimeAlert
for Sybase Replication Server packages should be upgraded for all
SunMC layers (server, agent and console).
- PrimeAlert for Sybase Replication Server packages on the SunMC
server host should be upgraded first. Then, agent hosts can be
upgraded according to any user defined schedule. Note that after the
server host is upgraded, the three included modules (PrimeAlert for
Sybase Replication Server, LogFileMonitor, and ProcessMonitor) should
continue to operate properly for all agent hosts, regardless of the
versions of the modules that are installed on an agent host. Finally,
after all server and agent hosts have been upgraded, the console
hosts should be upgraded to ensure that the module help documentation
is up-to-date.
- CAVEAT: After the server host has been upgraded, agent hosts that
contain older versions of PrimeAlert for Sybase may not have all of
the functionality of the newest module until the agent hosts have
also been upgraded to the same level as the server host.