Known Issues for Installation, Upgrade, and Deployment

Known issues and workarounds for installing, upgrading, and deploying Sybase Control Center.

Change Request Number	Description
700231	SCC cannot store an encrypted password for LDAP. SCC 3.2.6 and previous releases are distributed without a keystore used to encrypt and decrypt passwords stored in the LDAPLoginModule configuration block in csi_config.xml (in SCC 3.2.6 and later) or csi.properties (in SCC 3.2.5 and earlier). This does not affect SUP because the SUP distribution includes the keystore in question. Workaround: None.
698297	SCC does not support downgrade from a newer release to an older release. Workaround: If you need the ability to roll back an SCC upgrade, back up the SCC installation directory (SCC-3_2, SCC-3_1 , or SCC-3_0) before you upgrade.
677805	Cannot deploy a second SCC server instance on the same host. An error appears in agent.log: 2011-07-14 16:39:21,131 [ERROR] [asa.ASAInstanceManagerService ] [Agent Bootstrap Thread] - com.sybase.ua.service. AgentServiceException: Failed to start database engine com.sybase.ua.services.asa.ASAEngine$InvalidConnectionException: The connection to scc_repository is not valid. The file location /net/hmoconc/omni/cisqa/skibba/sccinstance_test/sybase/SCC-3_2/instances/sccnhrh564d. sybase.com/services/Repository/scc_repository.db does not match the file location specified in the service-config.xml (/net/hmoconc/omni/cisqa/skibba/sccinstance_test/sybase/SCC- 3_2/instances/instance2/services/Repository/scc_repository.db). This may indicate that another SCC repository server is running from a different installation directory and the connection is being made to the wrong server instance. Check to make sure any SCC repository servers running on the network each have a unique server name and tcp port. This problem does not occur if one of the instances is an SCC agent, which is a more common scenario. Workaround: Sybase does not recommend running more than one SCC server instance on a single host computer in a production environment. To enable a second server instance in a test or development environment: On the second SCC server instance, open this file: SCC-3_2/instances/<instance2>/services/SccSADataserver/service-config.xml Locate this line: <set-property property="com.sybase.asa.server.name" value="scc_repository" /> Change `scc_repository` to something different, such as `scc_repository2` or `scc_repository_instancename`. To display SCC ports that are in use, enter: scc --info ports See Configuring Ports in the online help for instructions on using the scc --ports command to reassign the ports on the second SCC instance. The two instances must use different ports.
586837	Sybase Control Center fails to start because it does not have enough memory. Workaround: For instructions on adjusting memory, see Get Started > Launching Sybase Control Center > Configuring Memory Usage in the SCC online help. In UNIX, you can also execute this command before starting SCC, 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.