Known Issues for Sybase Control Center

Known issues and workarounds for Sybase Control Center core functionality.

Change Request Number Description
643727

The browser crashes when you authenticate resources.

Workaround: If you are running Adobe Flash Player version 10.0 or earlier, upgrade to Flash Player 10.1 or later.

619406

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

If only one alert is configured for a resource, information is not updated on the Thresholds tab of the Alerts page in the Resource Properties dialog when you drop the alert.

Workaround: Close, then reopen the Resource Properties dialog. (In the Perspective Resources view, select the resource and select Resource > Properties > Alerts.)

618904 When you log in to Sybase Control Center in Windows Vista, an SSL handshake exception for a bad certificate appears in the agent log.

Workaround: You can safely ignore this exception.

618893

Attempts to access SCC online help immediately after SCC starts can result in an HTTP 404 “Not found” error.

Workaround: Wait a couple of minutes and try again.

618754

You cannot use incremental backups of the Sybase Control Center repository to recover the database.

Workaround:
  1. Shut down SCC.
  2. Open this file in a text editor: SCC-3_2/services/SccSADataserver/service-config.xml.
  3. Locate this line:
    <set-property property="com.sybase.asa.server.options" value="-m -qi -qw 
    -sb 0 -gn 100 -gm 500 -zl -zp" />
  4. Remove -m, so the line becomes:
    <set-property property="com.sybase.asa.server.options" value="-qi -qw 
    -sb 0 -gn 100 -gm 500 -zl -zp" />
  5. Save the changes and start SCC.

You can restore the repository database using incremental backups taken after this change.

607229 While executing the Agent Authentication, Server Start, Server Stop, and Errorlog View commands in Adaptive Server, you may experience performance degradation if there is a firewall between Sybase Control Center and the monitored Adaptive Server machines.

Communication between Sybase Control Center and a monitored Adaptive Server requires an RMI connection 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.

587717

Chart datatips appear in incorrect locations.

The datatips for all charts are showing up in incorrect locations. (A datatip is a tooltip 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.

586837

The SQL Anywhere repository database fails to start on SuSE Linux Enterprise Server 11 SP1, 64-bit.

Workaround: Execute this command before starting Sybase Control Center, or add it at the beginning of SCC-3_2/bin/scc.sh:
ulimit -v 59326240

The command increases the virtual memory available to Sybase Control Center.

576129

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.

560601

Cannot log in because the Sybase Control Center HTTP redirect fails when you use 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 SCC in IPv6 networks. For example:

https://sccxppro64.v6:8283/scc
558970 If you change the text size (Control+Alt++ or Control+Alt+-) for an SCC session in your browser, the change does not persist when you restart the browser.

Workaround: None.