Known issues and workarounds for Sybase Control Center for Adaptive Server.
Change Request Number | Description |
---|---|
696024 |
Cannot drop a thread pool when managing a cluster in Sybase Control Center. You cannot drop a thread pool when managing clusters. Dropping a thread pool from symmetric multiprocessing (SMP) systems is not affected by this problem. Workaround: Use isql or the Execute SQL tool in the SCC Administration Console to execute the drop thread pool command. The syntax is: drop thread pool <thread pool name> for instance <instance name> |
695138 |
Sybase Control Center cannot authenticate Unified Agent 2.5, and thus cannot view the log file or start Adaptive Server. You see this error:
User 'uafadmin' failed to authenticate with server 'ASE155x' agent. Login failed: No successful loginmodules. Please check credentials. Workaround: Use the new default password, Sybase4me, to authenticate Unified Agent. Sybase recommends that you change the default password immediately. |
692002 |
Instance level local engine group ID is not included in the generated DDL for an execution class. The DDL output generated from a local engine group that has been bound to an execution class for a shared disk cluster does not include instance ID for the instance. Workaround: Use sp_addexeclass from the Execute SQL view in the Administration Console. |
690795 |
After you change the kernel mode and restart the Adaptive Server, the Sybase Control Center monitor view may not update correctly, or may not correctly display that the kernel has been changed. When you change the kernel mode from either threaded to process or process to threaded in the Configuration screen of Sybase Control Center, and then restart the server, the monitor view may not update correctly or threads may still be displayed after changing to process mode. Workaround: When you change the server kernel mode in Adaptive Server 15.7 or higher, you may need to complete the following stepsto correctly display this resource in the monitor view.
|
679782 |
Cannot connect to a server.
Sybase Control Center for Adaptive Server cannot connect to Adaptive Server if the default network packet size is greater than 512KB. This issue is most commonly seen with SAP Business suite. Workaround: To connect to an Adaptive Server that has a default network packet size greater than 512 KB, edit this file: $SCC/plugins/ASEMAP/config.properties. Change
encrypt_network_password=true to
encrypt_network_password=false |
618901 |
Authentication of Unified Agent for Adaptive Server
15.5
or earlier fails on Windows.
The attempt to authenticate the Sybase Control
Center
with the Unified Agent managing an Adaptive Server fails when all
these conditions are met:
Workaround: Upgrade to Adaptive Server 15.5 ESD #1 or later. With Adaptive Server 15.5 GA, use the Simple Login Module of the Unified Agent to maintain a local list of logins and passwords for each Unified Agent installation. When you use the Simple Login Module, you must encrypt the password values using the passencrypt utility that is part of the Unified Agent installation. |
616855 |
The allocation information about devices for an Adaptive Server that
is configured to use the Chinese language and character set appears
in Chinese rather than in English.
To see allocation information, select Databases in the Adaptive Server Monitor, then click the Devices Used tab. Workaround: None. |
613300 |
Errors are reported on the Sybase Control Center console if a managed
Adaptive Server resource is unavailable.
Workaround: To prevent repeating error messages:
|
596022 |
The Adaptive Server Monitor screens for an Adaptive Server cluster
may not respond while a failover operation is occurring in the
cluster.
Workaround: None. |
589902 |
In some cases, Sybase Control Center displays incorrect values for
size and amount of space used by a segment in cluster
configurations.
This affects the data and charts that appear on the Details tab of the Segments screen in the Adaptive Server Monitor. Workaround: None. |
561126 |
After the Sybase Control Center automatically renames the agent.log file, it continues to write entries to the original log file. Workaround: None. |