 |
General Information | Provides information you should be aware of before you install and use Event Replicator for Adabas Open Systems Version 2.1 SP6. |
|
New Features and Enhancements | Provides information on new features/enhancements provided with this version. |
|
Migration | Provides information on migration for this version. |
|
Known Issues | Lists the product issues known at the time of the release. |
This part of the documentation provides information you should be aware of before you install and use Event Replicator for Adabas Open Systems.
The installation procedure requires ca. 10 MB disk space in the temporary directory (TEMP).
The product space requirements are documented in the Event Replicator for Adabas Open Systems manual.
Windows
Adabas 6.1 SP4 or later
Important:
Ensure that the Adabas License is authorized for usage with
Event Replicator for Adabas Open Systems.
Please refer to the document Release Notes for ConnecX SQL Engine, section Supported Platforms, Availability of CONNX Product Features for information describing the platforms on which the various Event Replicator components can be installed.
To install Event Replicator for Adabas Open Systems on your machine, please follow the instructions given in the Event Replicator for Adabas Open Systems Installation documentation.
Important:
Please consult the file INSTALL.TXT on the installation CD for
further details on installation issues.
Current users of Adabas installing Event Replicator for Adabas Open Systems for the first time, should check their Adabas license for the following line:
<Rex>yes</Rex>
Important:
If this line does not exist, you should apply for a new Adabas
license.
The Event Replicator for Adabas Open Systems will create the target files but will NOT replicate the data when the Adabas license is not authorized.
Before installing Open Systems Event Replicator, all databases that will be used as replication sources must be shutdown / terminated.
The following enhancements have been made for Initial State:
It is now possible to process multiple transactions as well as multiple initial states at one time.
Initial states are prioritized so that the largest tables are processed first. Combined with the ability to process multiple initial states at one time, this significantly reduces the overall time to complete the initial state process.
The start, stop and total time for the last initial state of each replication is now shown on the status tab.
The following enhancements have been made for Fault Tolerance:
In the event of a system crash, rather than forcing a redeploy and a new initial state, the Event Replicator will now attempt to recover its configuration files and continue replicating.
In the event of an SQL error on the target database, the Event Server will display the error and continue rather than taking replication off-line. This behavior is configurable.
In the event of losing connection with the target database, the Event Server will continue to retry the connection rather than go off-line.
The following enhancements have been made for Reporting and Statistics:
Greatly increased Server Status reporting.
It is now possible to report performance statistics.
Higher level of granularity. The status for each replication can be seen rather than just the event consumer.
The number of elements in the Message Queue is now displayed on the Server Status tab of the Replication Administrator.
Configurable debug levels for the EP, EC and controller allow the level of logging to be tuned based on specific needs.
Error messages can now be viewed directly from the GUI eliminating the need to review the log files.
The following additional enhancements are provided with this version:
Enhanced performance in the Message Queue as well as the Event Server.
Import and Export functions have been added to the Column Mapping screen.
Additional performance enhancements and bug fixes.
No migration is required when upgrading from previous versions.
This covers the product issues known at the time of release:
The installation terminates with an error, when the environment variable CONNXREGISTRY is not defined; e.g. the 32-bit version of the CONNX registry is not used.
The CONNXREGISTRY environment variable is created during the installation of the SQL Gateway and is a prerequisite for the Event Replicator for Adabas Open Systems.
This release of the Event Replicator for Adabas Open Systems does not provide support for Adabas 64-bit in Windows environments.
After installing Event Replicator for Adabas Open Systems, ensure that the Adabas license is authorized for use with Event Replicator for Adabas Open Systems. Check your Adabas license for the following line:
<Rex>yes</Rex>
If this line does not exist, you should apply for a new Adabas license.
After you have installed Event Replicator for Adabas Open Systems with a valid Adabas license, you must restart the database to pick up the new environment. If you attempt to restart the database without a valid license, the following warning message will be issued by the Adabas nucleus :
%ADANUC-W-LICREX, Usage of replication exit is not permitted by license
If the Adabas license is not authorized, the Event Replicator for Adabas Open Systems will create the target files, but will NOT replicate the data.
Note:
This message can also appear if the path setting to the replication
exit is invalid. In this case, Event Replicator for Adabas Open Systems should
be reinstalled.
Do not use localhost as the server name for the Adabas Source or Target tables. In certain instances using localhost as the server name may cause you to lose all your source table records during an initial state.
When you choose a source replication index, do not use a descriptor with the null suppression attribute set.
Null values within a null-suppressed descriptor cannot be replicated; if a descriptor contains null values the replication engine will disable during deployment. If the descriptor with the null suppression attribute set does not contain any null values, the tables will replicate but we recommend using another unique descriptor for replication.
If you use a descriptor with the Null Suppression attribute set you will get a warning if the CDD was created using SQL Gateway 6.6.1 or later; if the CDD was created in a prior versions the warning message will not appear.
The following restrictions apply when replicating from Adabas to Adabas.
The target table (FDT) must already exist in the Target database before replication, no target FDT will be created. The target and source tables must have the same structure.
Replication within one database is currently not supported.
Only flat tables can be replicated.
Subtables cannot be replicated, neither MU nor PE tables.
MU and PE fields must be rotated and referenced as a column of a flat table.
The number of occurrences of MUs and PEs is limited to a maximum of 191.
The maximum record size is limited to 64kb.
Files that have been defined with USERISN or file designs where the ISN is relevant should not be replicated.
The replicated data in the target database will not have the same ISN.
Do not replicate Unicode data from Adabas to DB2. The Replication tool does not currently support replicating Adabas Unicode data into a DB2 database.
Do not install the Event Replicator for Adabas Open Systems on an NFS share. Due to the NFS caching mechanism, replication cannot guarantee data consistency. When NFS data flows over the network, it adds an additional step in accessing the physical disk.
If the Open Systems Event Replicator does not initialize successfully, the Adabas database will continue to start, but no replication will be performed.
When the button is clicked, only the CONNX connections in the CDD are tested using the supplied logon credentials. The individual open systems Event Replicator components are not tested.
