IBM Support

Known Problems for Rational Synergy 7.2

Product documentation


Abstract

Known Problems for IBM Rational Synergy 7.2.

Content

APAR Internal ID Description/Workaround Status
PM00514 R#34527 The installation guide for Synergy 7.1 does not specify correct entries for Solaris 10 pam.conf.

The pam_unix.so.1 module is no longer supported under Solaris 10.

Workaround:

The following pam.conf settings can be used:

cmsynergy auth requisite pam_authtok_get.so.1
cmsynergy auth required pam_dhkeys.so.1
cmsynergy auth required pam_unix_cred.so.1
cmsynergy auth required pam_unix_auth.so.1
cmsynergy account required pam_unix_account.so.1

Deferred.
Possible fix pack candidate.
PM06267 R#35173 wastebasket directory defaults to %USERPROFILE% from the Synergy (Java) client

There is no way to specify a user-specific alternative path for the work area wastebasket
Deferred. Possible fix pack candidate.
PM20041 R#37396 Objects don't show in the Project tree table as work area conflicts are resolved Deferred. Possible fix pack candidate.
PM23430 R#37984 Conflict detection returns conflicts which are not real conflicts

Conflict detection will always report "Bad task" for any fix task even though the "bad task" is included in the project's update properties.
Deferred to future release.
PM25711 R#38463 Synergy is reporting an implicitly included conflict because of renamed object

The issue is that Synergy reports an implicitly included conflict for an object version in the baseline if that object version has been renamed in the current project.
Deferred to future release.
PM26688 R#38616 Canceling baseline creation does not clean up after itself

Canceling a baseline creation results in a baseline getting created in a 'deleted_baseline' state. Also it might contain newly created prep projects instead of static ones.

Workaround:

Either of the following steps may be used in Synergy CLI to remove such baselines and their associated projects and products.

Delete the baseline along with projects and products
ccm set role ccm_admin
ccm baseline -delete -with_projects_and_products baseline_spec

Remove baselines marked for deletion using SOAD
ccm set role ccm_admin
ccm soad -delete -scope "Baselines marked for deletion and related projects and products"

Planned to be fixed in Fix Pack 7.2.0.1.
PM27542 R#38744 Restarting ccm_server during an operation in the Java CLI results in a URE Deferred. Possible fix pack candidate.
PM27642 R#38773 Deleted file does not get deleted from all work areas

If a modifiable directory is used in multiple projects and these projects are handled by different clients, a change of the membership of the directory done in one project will not update the other projects work area.

Workaround:

A Sync can be used to detect the work area conflict created by the membership change in the other project and the conflict can be resolved to add or remove the files from the work area.
Deferred. Possible fix pack candidate.
PM29242 R#39008 "Out of Memory" error occurred after the network was disconnected and recovered during synchronizing Deferred. Possible fix pack candidate.
PM31992 R#39497 Sync Work Area ''additional patterns' inconsistently handled in HTTP and traditional modes Planned to be fixed in Fix Pack 7.2.0.1.
PM32083 R#39502 "Inconsistent" output of the "ccm attr" command in Synergy CLI Deferred. Possible fix pack candidate.
PM32198 R#39521 Synergy does not set baseline for new project groupings Deferred. Possible fix pack candidate.
PM32743 R#39618 Archive extraction hangs during fs_check Deferred. Possible fix pack candidate.
PM34480 R#38994 Better error messaging when using web mode without Unix account Deferred. Possible fix pack candidate.
PM34573 R#39911 Attempting to copy a release gives a URE Planned to be fixed in Fix Pack 7.2.0.1.
PM35238 R#40086 When using Web Mode keywords are always expanded.

If the expand on checkin option is not set, the files source will still be expanded during checkin if the object is placed in a copy based work area and a change has been done to that work area before the checkin, the file will be copied to the database at checkin time and the keywords within the file will be expanded during the copy.
Workaround: Make sure the file is synced to the cache before final test and checkin.
Planned to be fixed in Fix Pack 7.2.0.1.
PM35621 R#40088 Synergy copied Unix format files to Windows format during compare Planned to be fixed in Fix Pack 7.2.0.1.
PM36104 R#40160 Merged object in a shared project has a working status

In a shared project, when two versions are merged, the newly created version will have the status as 'working' when it should have been 'visible'.

Workaround
The object can be checked in to the visible state from the CLI.
Planned to be fixed in Fix Pack 7.2.0.1.
PM36105 R#40161 Folder query not updated across Synergy sessions Deferred. Possible fix pack candidate.
PM36154 R#40175 Synergy 7.1.0.2.02 in Web mode server lock with "java.io.IOException: Pipe closed", "SharedThreadPoolExecutor"

If project update adds a directory containing an object that has been cleaned from the cache using clean_cache, there is a possibility of deadlock during expansion of the files into the cache.

Workaround
If customers are experience server deadlock, recommend stop using the clean_cache command until this has been fixed.
Planned to be fixed in Fix Pack 7.2.0.1.
PM36372 R#40216 Work-Area path is sometimes not displayed in project properties pane Deferred. Possible fix pack candidate.
R#30479 Cannot change work area properties on inconsistent project hierarchy

If you have a project hierarchy with inconsistent work area properties - for example, some projects in the hierarchy have options such as 'Include project-specific directory in work area path' set and some have them unset - then attempts to change the work area properties for the entire hierarchy from the Synergy GUI or CLI will fail.

Workaround
Do any of the following:
a) Make the desired work area property changes individually on each project
b) Change individual work area properties to make the hierarchy consistent, and then set the desired properties on the entire hierarchy
Deferred to future release.
R#30637 Installation of Synergy on UNIX systems may give the message:

bsdtar: Failed to set default locale

Workaround
In the absence of any other errors or warnings, this message about the locale may safely be ignored.
Deferred to future release.
R#30657 Checked in files are modifiable in the work area even after unchecking the option 'Make all Files Modifiable'

When turning off the option "Make all files modifiable" in traditional mode, the files for all checked-in objects in the project will be made read-only. However, for web mode, checked-in files that have been modified will not have their permissions changed.

In both cases the conflict will be detected and reported to the user.

Deferred to future release.
R#32369 When moving a database from UNIX to Windows, the ccmdb unpack command leaves all cache files marked as read-only

When moving a database from UNIX to Windows, the ccmdb unpack command leaves cache files marked as read-only. This prevents Synergy from adjusting the access and modify times of the cache files to match the times stored in the database, which in turn will cause warnings from ccm fs_check.

Workaround:
To avoid these warnings, the CM administrator must bring up the Windows Properties dialog for the database’s st_root directory, unset the read-only flag, click Apply, and then check the option to apply to all subfolders and contents in the resulting prompt.
See also R#31030 - newlines in files must be converted when moving a database between Windows and UNIX. So, when moving from UNIX to Windows in 7.1, the user needs to run ccmdb upgrade -w AND clear the read-only Windows property as described in this CR.
Deferred to future release.
R#32673 No error to command line when trying to start a server when one is already running on the same host and port

If the server port is already in use by another process when server starts, the process fails with the following message in the server log file. (The server log file is located in $CCM_HOME/log/synergy_<host>_port.log):
2009-06-09T15:49:34.364-0700 WARNING: Failed to start: SocketListener0@0.0.0.0:8300 {org.mortbay.util.ThreadedServer}
Deferred to future release.
R#34132 Terminal invoked from synergy ( for editing or for exploring the directory) not able to display Unicode characters (Chinese characters). Deferred to future release.
R#34784 Warnings are reported when a database is upgraded in synergy_<database>_<server_port_number>.log

After upgrading a database, you might see error in the log that look like the following:

2009-12-03T12:58:14.167+0530 INFO : Server running in share session mode as user 'tester' for database \\win2k3r2-64vive\ccmdb\ibm. {sessionmgr}
2009-12-03T13:01:15.436+0530 SEVERE : Error allocating session {asyncarchiver.AsynchronousArchiver}
com.telelogic.cm.errorapi.CcmResourceException

During normal behavior, Synergy kicks off an asynchronous archiver automatically five minutes after the first user session is started, which in turn attempts to start a back-end session to serve its requests. While a database is being upgraded, Synergy attempts to kick off its asynchronous archiver but the back-end session startup fails, leaving these warning messages in the server log file. The messages, when occurring during upgrade, are harmless and the database upgrades successfully.
Deferred to future release.
R#39764 Failure message on compare of binary objects from CLI

It files being compared have binary content in them, then the default compare tool used by Synergy is reporting an error message such as “Diff/Merge Failed.”.

Workaround

Replace the default Synergy compare tool with one that can properly compare the binary files.

Deferred. Possible fix pack candidate.
R#40729 Incremental migrate command does not handle the case where the project is in static state.

If the specified project during incremental migrate is in static state, the migrate command will not report an error and will create an import package.
Deferred. Possible fix pack candidate.
R#40287 Import of a migrate package records Informix Error: Object 22465 - Could not create object.

The type specified for an object using migrate rule, if does not exist or is invalid in the underlying Synergy database, then migrate command is not reporting an error and is creating an import package. If such an import package is attempted to be imported into Synergy using import command then there will be errors reported during import operation.
Deferred. Possible fix pack candidate
R#40350 ccm merge creates file without any task associated to it.

From CLI, when ccm merge command is executed with no task specified and no default task set, a new merged version is created without any task associated to it.

Workaround
To ensure the newly created object is associated to a task, set the default task or specify the task in the merge command
ccm task -def <task_spec>
ccm merge file_spec1 file_spec2
or
ccm merge -task task_spec file_spec1 file_spec2
Planned to be fixed in Fix Pack 7.2.0.1.
R#40385 Migrate command cannot parse a rule file saved as UTF-8.

The migrate rules file if saved with UTF-8 encoding, is not getting parsed by the migrate framework.
Deferred. Possible fix pack candidate
R#40429 I/O problem when attempting to show Change Requests for baseline compare

There is a timeout that is elapsing before all the information from Change is received fore change requests.

Workaround
Find the following line in CCM_HOME/etc/ccm.properties:

ccm.properties:ccm.changerequesttool.timeout = 30000

Change the timeout from 30 seconds (i.e,. 30000 millisecnds) to 1 hour as follows:

ccm.properties:ccm.changerequesttool.timeout = 3600000
Planned to be fixed in Fix Pack 7.2.0.1.

Document information

More support for: Rational Synergy
Documentation

Software version: 7.2

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 7021292

Modified date: 13 May 2011