Known Issues for Sybase Control Center

After dropping an alert, the Thresholds tab is not refreshed.

If there is only one alert defined in Resource Properties > Alerts > Alert Management, the Thresholds tab is not refreshed after the alert is dropped.

Workaround: Close, then open Resource Properties > Alerts > Alert Management.

The agentd script for running Sybase Control Center 3.1 as a service in UNIX needs modifications.

Replace $SYBASE/SCC-3_1/bin/agentd with this script. Then follow the instructions for configuring Sybase Control Center to run as a service, found in “Starting and Stopping Sybase Control Center in UNIX” in the Sybase Control Center Installation Guide.

### begin script ###
#!/bin/sh
# chkconfig: 2345 90 10
# description: Starts and stops the Sybase Contol Center daemon.
#
# Sybase Control Center (SCC) daemon
#
# Usage:
#   This script must be installed in your platform's startup
#   directory (/etc/init.d on Linux) and enabled using the
#   platform's standard tools (i.e. chkconfig on linux).
#
#   Important: Before installing this script, you must edit it
#   to set SYBASE to the Sybase Install directory containing SCC.
#
SYBASE=<Replace_with_path_to_parent_directory_of_SCC-3_1>
SCC_HOME=${SYBASE}/SCC-3_1

. ${SYBASE}/SYBASE.sh

if [ -d ${SCC_HOME} ]; then
  echo SCC Home: ${SCC_HOME}
else
  echo SCC_HOME variable not set to a valid Sybase Control Center install directory
  exit 1
fi

case "$1" in
start)
    cd ${SCC_HOME}/bin
    ./scc.sh --start 2>&1 >> ${SCC_HOME}/log/scc-console.out &
    echo Started SCC.  Output can be found at ${SCC_HOME}/log/scc-console.out
    ;;

stop)
    cd ${SCC_HOME}/bin
    ./scc.sh --stop
    ;;

status)
    cd ${SCC_HOME}/bin
    ./scc.sh --status
    ;;

restart)
    cd ${SCC_HOME}/bin
    ./scc.sh --stop
    ./scc.sh --start 2>&1 >> ${SCC_HOME}/log/scc-console.out &
    echo Started SCC.  Output can be found at ${SCC_HOME}/log/scc-console.out
    ;;

*)
    echo "Usage: $0 { start | stop | restart | status }"
    exit 1
    ;;
esac

exit 0
### end script ###

Resolution e-mail is inconsistent and does not reach all users.

When an alert is resolved, every user with active subscriptions to the alert is supposed to receive e-mail explaining that the alert condition has been resolved. Instead, the subscription selected in the property sheet at the time the alert was resolved determines which users are e-mailed. If there are no subscriptions, then no informative e-mail is sent. If the alert is critical, but the warning subscription is selected, the e-mail is sent to the warning subscribers.

Workaround: None.

Alert resolution after subscription creation or modification fails.

Alert resolution fails with this message:

Resolve alert failed. Alert resolution failed. java.lang.Exception : Alert not found in sendResponseMessage(): alert_name

Workaround: Close the properties sheet after adding or modifying subscriptions.

Collection history cannot be viewed using a Web browser with Flash Player 10.0.42.34 on 32-bit machines running RedHat 5 Linux.

Workaround: Use a browser with an older version of the Flash Player or use a browser on a different platform.

Communication between Sybase Control Center and a monitored Adaptive Server requires an RMI connection to be established between Sybase Control Center and the Unified Agent of the Adaptive Server. If a firewall prevents these connections from being established, performance may degrade.

Workaround: None.

A right click does not highlight the resource being acted on.

If you left-click to select a resource in the Perspective Resources view then right-click a different resource, the first resource remains visibly selected. However, if you select an option from the context menu, it is applied to the second (right-clicked) resource.

Chart datatips appear in incorrect locations.

The datatips for all charts are showing up in incorrect locations. (A datatip is a tool tip that displays the data value for a particular spot on a graph or chart when you mouse over that spot.) This occurs in all component plug-ins.

Workaround: None. This is an Adobe Flex SDK issue.

Pressing F5 to refresh your browser logs you out of Sybase Control Center.

Browser refresh does not refresh data inside Sybase Control Center, but refreshes the loaded application or pages in the browser—in this case, the Adobe Flash on which Sybase Control Center is built. Consequently, pressing F5 logs you out of any servers you are currently logged in to, including Sybase Control Center.

Workaround: Do not use F5 when you are logged in to Sybase Control Center.

Cannot connect to Sybase Control Center using IPv6 format.

If you use an IPv6 HTTP URL for Sybase Control Center, it does not redirect to HTTPS as it should. For example, this URL does not work:

http://sccxppro64.v6:8282/scc

Workaround: Use a URL with the HTTPS format and port to connect to Sybase Control Center in IPv6 networks. For example:

https://sccxppro64.v6:8283/scc