Known Issues for Installation, Upgrade, and Deployment

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

Change Request Number	Description
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`.
586837	The Sybase Control Center repository, a SQL Anywhere database, fails to start on SuSE Linux Enterprise Server 11 SP1, 64-bit. Workaround: 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.

Change Request Number

Description

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.

586837

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

Workaround: 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.