Known Issues for Installation, Upgrade, and Deployment

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

Change Request Number	Description
680008	Upgrade from SCC for Replication 3.0 to 3.2.3 fails. Adaptive Server resources do not display or function properly. Workarounds: Do either of the following: Reauthenticate the affected Adaptive Servers: In the Perspective Resources view, select one or more Adaptive Servers. Select Resource > Clear Authentication. Select one of the cleared Adaptive Servers and select Resource > Authenticate. Enter login ID and password at the prompts. Repeat for any remaining Adaptive Servers that require authentication. Starting from the SCC 3.0 installation, upgrade to 3.1, then upgrade again from 3.1 to 3.2.3.
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`.

Change Request Number

Description

680008

Upgrade from SCC for Replication 3.0 to 3.2.3 fails.

Adaptive Server resources do not display or function properly.

Workarounds: Do either of the following:

Reauthenticate the affected Adaptive Servers:
1. In the Perspective Resources view, select one or more Adaptive Servers.
2. Select Resource > Clear Authentication.
3. Select one of the cleared Adaptive Servers and select Resource > Authenticate. Enter login ID and password at the prompts.
4. Repeat for any remaining Adaptive Servers that require authentication.
Starting from the SCC 3.0 installation, upgrade to 3.1, then upgrade again from 3.1 to 3.2.3.

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.