IBM Rational Synergy 7.2.2.2 has been made generally available and contains new features as well as fixes for client-reported and internally found defects.
Table of Contents
| Sections |
Description |
|
|
The Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable.
|
|
|
This section provides information related to the impact of this release to allow you to assess how your environment may be affected.
|
|
|
This section provides important information to review prior to the installation of this release.
|
|
|
This section provides the direct link to obtain the download package for installation in your environment.
|
|
|
This section provides the installation instructions necessary to apply this release into your environment.
|
|
|
The Known side effects section contains a link to the known problems (open defects) identified at the time of this release.
|
Supporting Documentation
| Document |
Description |
|
|
Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.
|
|
|
The information center provides you with user assistance for the product. You can view, browse, and search online information related to the product. You can also visit IBM Product information page to browse for additional information centers.
|
|
|
Click to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family.
|
Deliverable Synergy Components Affected
Database files affected by the Fix Pack:
Database_Path/lib/apilib.a
CCM_HOME files affected by the Fix Pack:
$CCM_HOME/bin/ccm
$CCM_HOME/bin/ccmdb
$CCM_HOME/bin/ccm_rsh
$CCM_HOME/bin/ccm_aci
$CCM_HOME/bin/ccm_acc
$CCM_HOME/bin/ccmdb_ora
$CCM_HOME/bin/dbutil/ccmdb_info_inf
$CCM_HOME/bin/dbutil/ccmdb_update
$CCM_HOME/bin/dbutil/ccmdb_clear_binvals
$CCM_HOME/bin/dbutil/ccmdb_table_inf
$CCM_HOME/bin/dbutil/ccmdb_serverinfo_inf
$CCM_HOME/bin/dbutil/ccmdb_refchk_inf
$CCM_HOME/bin/dbutil/ccmdb_dbsinfo_inf
$CCM_HOME/bin/dbutil/ccmdb_names_inf
$CCM_HOME/bin/dbutil/ccmdb_mkdbs_inf
$CCM_HOME/bin/dbutil/ccmdb_lock_inf
$CCM_HOME/bin/dbutil/ccmdb_load_inf
$CCM_HOME/bin/dbutil/ccmdb_index_inf
$CCM_HOME/bin/dbutil/ccmdb_dump_inf
$CCM_HOME/bin/dbutil/ccmdb_clear_binvals_ora
$CCM_HOME/bin/dbutil/ccmdb_dump_ora
$CCM_HOME/bin/dbutil/ccmdb_index_ora
$CCM_HOME/bin/dbutil/ccmdb_info_ora
$CCM_HOME/bin/dbutil/ccmdb_load_ora
$CCM_HOME/bin/dbutil/ccmdb_lock_ora
$CCM_HOME/bin/dbutil/ccmdb_names_ora
$CCM_HOME/bin/dbutil/ccmdb_refchk_ora
$CCM_HOME/bin/dbutil/ccmdb_table_ora
$CCM_HOME/bin/dbutil/ccmdb_update_ora
$CCM_HOME/bin/util/ccm_eng_inf
$CCM_HOME/bin/util/bsdlog
$CCM_HOME/bin/util/bsdrcs
$CCM_HOME/bin/util/bsdco
$CCM_HOME/bin/util/bsdci
$CCM_HOME/bin/util/ccm_unzip
$CCM_HOME/bin/util/ccm_zip
$CCM_HOME/bin/util/ccm_fix_router
$CCM_HOME/bin/util/ccm_sort
$CCM_HOME/bin/util/ccm_pwd
$CCM_HOME/bin/util/ccm_logger
$CCM_HOME/bin/util/ccm_install_util
$CCM_HOME/bin/util/ccm_hostname
$CCM_HOME/bin/util/ccm_hexdec
$CCM_HOME/bin/util/ccm_file_stat
$CCM_HOME/bin/util/ccm_sync_files
$CCM_HOME/bin/util/ccm_seng.nt
$CCM_HOME/bin/util/ccm_receive
$CCM_HOME/bin/util/ccm_ci
$CCM_HOME/bin/util/bsddff3
$CCM_HOME/bin/util/bsddff
$CCM_HOME/bin/util/ccm_eng_ora
$CCM_HOME/lib/informix_files
$CCM_HOME/lib/ccm_files
$CCM_HOME/lib/jre_files
$CCM_HOME/lib/ccmjava.jar
$CCM_HOME/lib/libmakeenv.so
$CCM_HOME/lib/libaccent.so
Installation Instruction (LINUX)
Before you begin, make sure that you have performed a successful backup of your Synergy installation areas.
This Fix Pack contains modifications to the software that must be installed in the installation directory (CCM_HOME changes). This Fix Pack also contains changes for cache server and if there are any cache servers installed then they must be updated (Cache server changes). Once you have installed Fix Pack 7.2.2.2, do not install any individual iFix or Fix Pack that does not clearly state that it may be installed on top of Fix Pack 7.2.2.2, unless informed otherwise by Synergy Support.
- In preparation for the following steps, ask all users to exit their Synergy sessions.
- Login as user ccm_root and set CCM_HOME to point to your Synergy installation. Shut down all Synergy 7.2.2 databases to be patched. Verify that all users have exited by using the ccm monitor command.
$su - ccm_root
ccm_root$ CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
ccm_root$ PATH=$CCM_HOME/bin: $PATH
ccm_root$ export CCM_HOME PATH
ccm_root$ ccmdb shutdown <dbpath> # Repeat per database
ccm_root$ ccm monitor
Stop the Synergy daemons using the “ccm_stop_daemons” command.
ccm_root$ ccm_stop_daemons
- Update the Synergy installation directory.
Use the ccm_patch command. The argument to ccm_patch is the full path to the Fix Pack file that you are installing.
Note that ccm_patch must be run as root, since it needs to set ownership and permissions on the patched files.
ccm_root$ su
# CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
# PATH=$CCM_HOME/bin: $PATH
# export CCM_HOME PATH
If your database runs on Oracle, then set ORACLE_HOME
# ORACLE_HOME=/usr/local/oracle # Adjust as appropriate
# export ORACLE_HOME
Linux:
# ccm_patch <PATH>/7.2.2.2-Rational-RATISYNE-Linux-FP02.tar.gz
# exit
AIX:
# ccm_patch <PATH>/7.2-RATL-RATISYNE-AIX-FP2.2.tar.gz
# exit
Repeat this command for each installation directory.
Once the installation directory has been updated the Synergy daemons should be restarted as ccm_root user.
ccm_root$ ccm_start_daemons
- If there are cache servers installed, they also need to be updated. (Run the commands on the cache server system, if the cache servers are running on Windows platform, refer the Windows installation section)
ccm_root$ su
# CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
# PATH=$CCM_HOME/bin: $PATH
# export CCM_HOME PATH
# cd $CCM_HOME/bin
Use the tar file that is appropriate for your UNIX platform. The tar files will be available in the Synergy run area under the path CCM_HOME/cacheserver
For AIX:
#cacheserver_patch <PATH>/cacheserver_7.2-2.2-aix.tar.gz
For Linux:
#cacheserver_patch <PATH>/cacheserver_7.2-2.2-linux.tar.gz
Repeat this command for each installation directory.
- Once the installation directory has been updated, restart the Synergy cache server as the ccm_root user.
ccm_root$ ccm_cache -start
- Use the ccm_patch command to apply this Fix Pack to one or more databases.
If you have a customized model using a custom model database, you should contact Synergy Support for assistance.
Databases that where shut down in step ‘2’ must be unprotected prior to patching.
$ su - ccm_root
ccm_root$ CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
ccm_root$ PATH=$CCM_HOME/bin: $PATH
ccm_root$ export CCM_HOME PATH
ccm_root$ ccmdb unprotect <dbpath>
ccm_root$ ccm_patch -dbonly $CCM_HOME/patches/7.2.2.2 <dbpath>
-
Inform users that they can restart their Synergy sessions.
This Fix Pack contains a Windows client component. Users of Synergy Windows GUI will be prompted to download the Fix Pack when they start a session. Users of Windows CLI clients should be requested to patch their clients by browsing to
http://<helpserver>:<port#>/client/Update_7.2-2.2.exe.
Alternatively, the executable, Update_7.2-2.2.exe, can be distributed to Windows CLI users so they can execute it directly, to update their client installations.
Reversing Fix Pack (LINUX)
If it is necessary to remove the Fix Pack after it was installed, follow these steps. Users with Windows clients should reference the Windows section of this readme for reversing the Fix Pack on their clients.
-
In preparation for the following steps, ask all users to exit their Synergy sessions. As 'ccm_root', shut down all Synergy databases that were patched with Fix Pack 7.2.2.2. verify that all users have exited by using ccm monitor.
$ su - ccm_root
ccm_root$ CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
ccm_root$ PATH=$CCM_HOME/bin: $PATH
ccm_root$ export CCM_HOME PATH
ccm_root$ ccmdb shutdown <dbpath> # Repeat per database
ccm_root$ ccm monitor
Stop the Synergy daemons using the ccm_stop_daemons command.
ccm_root$ ccm_stop_daemons
-
Restore the installation files from before Fix Pack 7.2.2.2
$CCM_HOME contains a save directory structure that contains all files that were removed or replaced during the Fix Pack installation process. The files are saved with a suffix of _p7.2.2.2. In addition, the first time a particular file is saved it will also be saved with an extension of _orig. All files that were updated with this Fix Pack should be replaced. For a complete list of $CCM_HOME files that were changed see section
DELIVERABLE SYNERGY COMPONENTS AFFECTED.
For example, $CCM_HOME/lib/ccmjava.jar was replaced, to replace it with the file from before this Fix Pack:
ccm_root$ cp $CCM_HOME/save/lib/ccmjava.jar_p7.2.2.2 \
$CCM_HOME/lib/ccmjava.jar
Or
Restore the original 7.2.2 installation files:
ccm_root$ cp $CCM_HOME/save/lib/ccmjava.jar_orig \
$CCM_HOME/lib/ccmjava.jar
Repeat this step for each $CCM_HOME file listed in
DELIVERABLE SYNERGY COMPONENTS AFFECTED
-
Remove entries in patches.txt and patches.dat
In the $CCM_HOME%/etc directory are files patches.txt and patches.dat. Using an editor, for instance vi, edit these files. Remove the lines referencing this Fix Pack.
Save this file and exit the editor. If the resulting files are empty, then they should be deleted.
-
Login as user 'root'. You need to run $CCM_HOME/bin/ccm_install in order to reset the ownership and permissions of the original files you copied back:
$ su -
# CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
# PATH=$CCM_HOME/bin: $PATH
# export CCM_HOME PATH
If your database runs on Oracle, then set ORACLE_HOME
# ORACLE_HOME=/usr/local/oracle # Adjust as appropriate
# export ORACLE_HOME
# ccm_install -c
# exit
If the cache server was patched, then Login as user root on cache server. You need to run $CCM_HOME/bin/cacheserver_install in order to reset the ownership and permissions of the original files you copied back:
$ su -
# CCM_HOME=/usr/local/ccm722 # Adjust as appropriate
# PATH=$CCM_HOME/bin:$PATH
# export CCM_HOME PATH
# cacheserver_install -c
# exit
-
Reverse Fix Pack 7.2.2.2 in databases.
If you have a customized model, using a model database, reinstate your previous model by performing a model install from your original customized model project to each database.
Each database directory contains a save directory structure that contains all files that were removed or replaced during the Fix Pack installation process. The files are saved with a suffix of _p7.2.2.2. In addition, the first time a particular file is saved it will also be saved with an extension of _orig. All files that were updated with this Fix Pack should be replaced. For a complete list of database files that were changed see section
DELIVERABLE SYNERGY COMPONENTS AFFECTED.
For example, <dbpath>/lib/apilib.a was replaced, to replace it with the file from before this Fix Pack:
ccm_root$ cp <dbpath>/save/lib/apilib.a_p7.2.2.2 <dbpath>/lib/apilib.a
Or,
Restore the original 7.2.2 file:
ccm_root$ cp <dbpath>/save/lib/apilib.a_orig <dbpath>/lib/apilib.a
Repeat this step for each database file listed in
DELIVERABLE SYNERGY COMPONENTS AFFECTED
In the <database path>/db directory of each database is a file named MDL_INFO. Using an editor, for instance vi, edit these files. Remove the lines referencing this Fix Pack.
In the <database path>/etc directory of each database is a file named patches.dat. Using an editor, for instance vi, edit these files. Remove the lines referencing this Fix Pack.
Save these files and exit the editor. If the resulting files are empty, then they should be deleted.
-
Unprotect the databases that were shut down in step 1, using:
ccm_root$ ccmdb unprotect <dbpath>
Repeat for every database that was patched.
- Start the Synergy daemons using the ccm_start_daemons command.
ccm_root$ ccm_start_daemons.
- Inform users that they can restart their Synergy sessions.
Installation Instructions (WINDOWS)
Before you begin, make sure that you have performed a successful backup of your Synergy databases and Installation areas. These backups are the only supported means of reversing the installation of this Fix Pack into Synergy databases.
This Fix Pack contains changes that must be installed in Synergy databases (model changes). This Fix Pack also contains modifications to the software that must be installed in the installation directory (CCM_HOME changes).
Once you have installed Fix Pack 7.2.2.2, you should not install any individual iFix that does not clearly state that it may be installed on top of Fix Pack 7.2.2.2, unless informed otherwise by Synergy Support.
-
Request that all users exit their Synergy sessions before you begin the installation.
Shutdown all Synergy databases using the "ccmdb shutdown" command.
Verify that all users have exited by using the "ccm monitor" command.
> ccmdb shutdown <dbpath> # Repeat per database
> ccm monitor
- If Rational Change or Rational Synergy Integrations are running, shut them down.
- To apply the Fix Pack to a Windows Synergy server installation, you must log in as a user in the Local Administrator group on the Main or Additional server machine. Do not install the Fix Pack on your computer if you use a shared network installation; just install the Fix Pack once on the network installation.
- Once you have logged in as the appropriate user, run the Fix Pack executable, 7.2.2.2-Rational-RATISYNE-Windows-FP02.exe from the command prompt or by double clicking it. This brings up the Patch Installation Utility which guides you through the steps of installing the Fix Pack.
-
To run ccm_addsrv command you must download and install "
vc_redist.x86.exe".
Open CM Command prompt as administrator on the main server and run the following command:
ccm_addsrv <mainserverhostname>
-
If you have additional Database server, Open Command Prompt as administrator on the additional database server and run below command after installing the Fix Pack 7.2.2.2-Rational-RATISYNE-Windows-FP02.exe.
> ccm_addsrv <mainserverhostname>
-
Start the Windows services ccm7.2.2_* from service control manager.
If the cache servers are installed, then the cacheserver service need to be stopped from services dialog on the cacheserver host. Once the cacheserver service is stopped, the cache server run area need to be patched by running the executable cacheserver_7.2.2.2-windows.exe from the command prompt or by double clicking it. This brings up the Patch Installation Utility which guides you through the steps of installing the Fix Pack on cache server. Start the cache server service once the installation is completed. Cacheserver_7.2.2.2-windows.exe will be available in the Synergy server run area under the path %CCM_HOME%\cacheserver.
-
Patch standard databases.
If you do not have a customized model, apply this Fix Pack to each of your databases. All databases must be patched prior to use with this Fix Pack.
If you have a customized model using a custom model database, contact Synergy support for assistance.
To patch a database on a Windows server, use the batch script that was extracted when you ran the self-extracting patch executable on the server. This script needs to be given the database path of the database(s) to be patched.
Log in as CM administrator on the Main or Additional Server machine for the database being patched and bring up a command window. Repeat the following commands for each database:
> set CCM_HOME= C:\Program Files (x86) \IBM\Rational\Synergy\7.2.2
> set PATH=%CCM_HOME%\bin;%PATH%
> ccmdb unprotect <dbpath>
> ccmdb_patch_7222 <dbpath>
> postdb_7222.bat <dbpath> <host> <admin_user> <admin_user_password>
Note that passwords often contain characters that are interpreted by the shell, such as spaces, semicolons, wild cards, etc. If this is the case, then be sure to type your admin user password in quotes.
-
Inform users that they can restart their Synergy sessions.
This Fix Pack contains a Windows client component. Users of the Synergy Windows GUI will be prompted to download the Fix Pack when they start a session. Users of the Windows CLI will be requested to patch their clients by browsing to:
http://helpserver:port#/client/Update_7.2-2.2.exe.
Alternatively, the executable Update_7.2-2.2.exe can be distributed to Windows client users, so they can execute it directly, to update their client installations.
Reversing Fix Pack (WINDOWS)
If it is necessary to remove the Fix Pack after it was installed follow these steps; they must be performed by a Synergy database administrator.
- Request that all users exit their Synergy sessions before you begin the uninstallation. Shutdown all Synergy databases using the ccmdb shutdown command. Verify that all users have exited with ccm monitor.
> ccmdb shutdown <dbpath> # repeat per database
> ccm monitor
- Stop the 7.2.2 Synergy services. Perform this step as an admin user. Open the services dialog and stop the Synergy services. If the cache servers are installed, then the cache server service also need to be stopped from services dialog..
-
Restore the original files replaced by Fix Pack 7.2.2.2
Before replacing the original files, remove the hidden attribute from files stored under the %CCM_HOME%\patches\7.2.2.2 directory and its subdirectories.
Do this as user who has local admin rights. Use the attrib command to remove the Hidden attribute from the files. From a command prompt:> cd %CCM_HOME%\patches\7.2.2.2
> attrib -h * /s /d
The %CCM_HOME%\patches\7.2.2.2 directory contains two files and either three or four sub-directories. The two files are a README file and ccm_bp.in. You do not need to be concerned with the ccm_bp.ini file.
The three sub-directories that every installation will have are CCM_HOME, util, and WINSYS. If your installation contains the Synergy Database Administration Tools, there will be an additional sub-directory named database. This last directory is not hidden and the files it contains are not hidden.
The util and WINSYS directories are empty and can be ignored. The database directory may also be ignored for 7.2.2.2 as there are no database components in this Fix Pack.
-
The CCM_HOME directory contains a directory structure similar to that of your Synergy installation area. Any files that were removed or replaced from your installation area are under this directory.
After removing the hidden attribute from all of the files stored under this CCM_HOME directory and its sub-directories, copy or move all of these files into the Synergy installation area directory structure, replacing the files that are currently there.
Example:
a. Replace “ccm_exec” from %CCM_HOME%\patches\7.2.2.2\CCM_HOME\bin\util to %CCM_HOME%\bin\util
b. Replace "ccmdb" and "ccmsrv" from %CCM_HOME%\patches\7.2.2.2\CCM_HOME\bin to %CCM_HOME%\bin\
c. Remove ccm_addsrv file from %CCM_HOME%\bin
d. Change the name of file “sqlhosts.<hostname>” to "sqlhosts" from %CCM_HOME%\informix\etc
Note: If you are reversing from 7.2.2.2 to Synergy 7.2.2 then only the below steps need to be performed.
I. Remove ccm_addsrv file from %CCM_HOME%\bin
II. Change the name of file “sqlhosts.<hostname>” to "sqlhosts" from %CCM_HOME%\informix\etc
Edit the registry Key value "INFORMIXSQLHOSTS" from
> HKLM\SOFTWARE\Informix\OnLine\<INFORMIXSERVER>\Environment
Modify key value to %CCM_HOME%\informix\etc\sqlhosts
-
Remove entries in patches.txt and patches.dat in both Synergy server and also from cache servers if they were patched.
In the %CCM_HOME%\etc directory are files “patches.txt” and “patches.dat”
a. Using a text file editor (such as Notepad.exe)
b. Edit these files and remove the lines referencing this Fix Pack.
c. Save this file and exit the editor.
d. If the resulting files are empty, then delete them.
-
Remove 7.2.2.2 Key from the Registry.
a. Start the registry editor (Click Start > Run type regedit)
b. Browse to the appropriate key listed below.
c. You will see a key labelled 7.2.2.2. Click it. (HKEY_LOCAL_MACHINE\SOFTWARE\Telelogic\CM SYNERGY\7.2.2\Install\Patches\7.2.2.2)
d. Delete the key (press Delete on keyboard).
e. Exit the registry editor.
NOTE: Repeat the above steps for Additional DB server also while reversing Fix Pack.
-
Reverse Fix Pack 7.2.2.2 in databases
If you have a customized model, using a model database, reinstate your previous model by performing a model install from your original customized model project to each database.
If you used ccmdb_patch_7222.bat to install Fix Pack to your databases, the following steps are performed when "ccmdb_patch_7222 is run:
Before the Fix Pack is applied, affected database files are copied to <dbpath>\save\<filename>.p7222
The updated files from the Fix Pack are copied to the database.
A line is appended to <database path>\db\MDL_INFO as a record of the Fix Pack.
To reverse these actions, perform the following steps for each patched database.
Log in as CM administrator on the database server machine and bring up a command window.
Remove the database files that were changed:
> del <dbpath>\lib\apilib.a
Move the saved copy of these files back into their original locations:
> move <dbpath>\save\lib\apilib.a.p7222 <dbpath>\lib\apilib.a
Repeat this step for each database file listed in Database files affected by the Fix pack.
In the <database path>\db directory, there is a file named MDL_INFO.
Using a text file editor (such as Notepad.exe), edit this file and remove the lines referencing this Fix Pack. Save this file and exit the editor.
In the <database path>\etc directory is a file named patches.dat.
Using a text file editor (such as Notepad.exe), edit this file and remove the line referencing this Fix Pack. Save this file and exit the editor. If the resulting files are empty, delete them.
- Restart the services that were stopped in step 2. Open the services dialog and start the Synergy services.
Also, If the cache servers are installed, then the cacheserver service also need to be restarted from services dialog.
- Unprotect the databases that were shut down in step 1
> ccmdb unprotect <dbpath>
Repeat for every database.
NOTE: Inform users that they can restart their Synergy sessions.
Review the installation guide:
|
Click on the relevant links below for Installation Instructions for Windows, UNIX with Informix, or UNIX with Oracle.
|
[{"INLabel":"Installing Rational Synergy on Windows","INLang":"English","INSize":"1 B","INURL":"https://www.ibm.com/support/knowledgecenter/SSRNYG_7.2.1/com.ibm.rational.synergy.install.win.doc/topics/sg_c_igw_install_on_win.html"},{"INLabel":"Installing Rational Synergy on UNIX with Informix","INLang":"English","INSize":"1 B","INURL":"https://www.ibm.com/support/knowledgecenter/SSRNYG_7.2.1/com.ibm.rational.synergy.install.unix.informix.doc/topics/s_c_igu_install_on_unix.html"},{"INLabel":"Installing Rational Synergy on UNIX with Oracle","INLang":"English","INSize":"1 B","INURL":"https://www.ibm.com/support/knowledgecenter/SSRNYG_7.2.1/com.ibm.rational.synergy.install.unix.oracle.doc/topics/s_c_igu_install_on_unix.html"}]
Download options
| Download |
RELEASE DATE |
LANGUAGE |
Download Options
|
|
|
01-December-2020
|
English |
FC |
Impact Assessment
| Impact |
Description |
|
Recommended
|
This is a service release of Rational Synergy. It contains new features as well as fixes for client-reported and internally found defects.
|
Definitions
Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:
- Coding errors that cause a regression
- Documentation or packaging problems that cause a regression
- Errors reported in a new function delivered in a MDV that cause a regression
Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:
- Fixed APARs which did not solve the original problem but did not break anything new
- APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression
Notes:
- Regression and incomplete APARs are considered fix-in-error or MDV-in-error
- Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
- Issues in major releases due to new functionality do not apply in this definition
|
There are no known issues to report.
|
Click the
Fix List link in the table of contents above to review a list of the problems solved in this release.
|
Review the following list of open defects:
|
Known Issues in Rational Synergy 7.2.2.2 on Linux platform
|
|
Problem/Workaround
|
| As rcp protocol is not supported and synergy is not updated with secure protocols to connect remotely, we are unable to test Remote Transfer and FTP. |
Not Available |
| Informix database creation fails when the default value of root.dbs is set as 63488 KB. |
Workaround for creating Informix server database while changing the default size of the chunk file.
i. Create the Informix Database with size of root.dbs as 300 MB.
ii. If required, using the ccmsrv expand command you can further increase the size of logical files.
|
| Informix server will not come online with ccmsrv online -s <servername> , once made it offline ccmsrv offline -s <servername> |
i. Reboot the machine.
ii. Bring the informix online using ccmsrv online -s <servername>. |
Known Issues in Rational Synergy 7.2.2.2 on Windows platform
|
|
Problem/Workaround
|
| As rcp protocol is not supported and synergy is not updated with secure protocols to connect remotely, we are unable to test Remote Transfer and FTP. |
Not Available |
|
Help server doesn't start by default after installing Synergy.
|
Start manually from services windows ccm7.2.2_helpsrv. |
Known Issues in Rational Synergy 7.2.2.2 on AIX platform
|
|
Problem/Workaround
|
| As RCTP protocol is not supported and Synergy is not updated with secure protocols to connect remotely, Remote Transfer and FTP DCM transfer modes were not tested. |
Not Available |
| Synergy session cannot start with the error "Informix: Network connection is broken". |
Restart all Synergy processes using "ccm_start_daemons". Then bring the Informix server online using "ccmsrv online[ -s servername]". |
| Informix Server cannot be brought online while being taken offline, throwing error message "oninit: Fatal error in shared memory creation". |
Delete all the shared memory ID segments associated with group/owner “informix”. Bring the Informix server online using the “ccmsrv online [-s servername]” command. |
Rational Synergy 7.2.2.2 includes the following enhancements:
Updated Platform Support
- Oracle 18c Server support with Oracle 12c client
- Rational Synergy Support for RHEL 7.7 and 7.8
- Improved Synergy GUI performance when defining more file types.
Off
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSC6Q5","label":"Rational Synergy"},"ARM Category":[],"Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.2.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Problems (APARS) fixed
Problems (APARS) fixed