Known Issues for Sybase Control Center

Known issues and workarounds for Sybase Control Center core functionality, which is present in all product modules.

Change Request Number Description

697145

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. Delete this line:
    <set-property property="com.sybase.asa.database.options" value="-m" />
  4. Save the changes and start SCC.

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

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.

587717

Datatips in monitoring views and the statistics chart appear in fixed locations on the browser screen regardless of where the chart is located. If you move the chart on the screen, the datatips do not move with the chart.

(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 product module plug-ins.

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

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://myscc64.v6:8282/scc

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

https://myscc64.v6:8283/scc