|
DBMoto (formerly DB2Motion) Release
Notes
Click here
to view a list of OLE DB Providers and ODBC Drivers that have been
tested with DBMoto.
|
Version
|
Date
|
Data
Replicator/User Interface changes
|
| 4.01.09 |
11/14/05 |
- Fixed an error in Oracle when reading the last redo log id, the field
apt to contain the Sequence value of the Redo log was underdimensioned and
might cause overflow errors.
- Exposed to the script the function TryReOpen that is used to close a
connection and reopen it. This can be used from script in some cases when
it is necessary to reset the connection to clean up temporary objects in
the server.
- Introduced support for double byte in the metadata of SQL Server.
Now even object names for SQL Server defined in double byte can be
retrieved from DBMoto.
- Fixed a problem with MySQL, when creating a replication with MySQL as
target a message would come up saying that no library or database has been
defined in the connection string.
- Fixed a problem in Oracle when detecting the right version of the
server to take the appropriate steps for replication.
- Resolved a syntax error in Oracle when opening the logminer in
versions previous than 9.2 with the use of the online dictionary.
- Fixed an error on SQL Server as source, the SQL Server name
was mistaken when the SQL Server instance was defined as an IP address.
|
| 4.01.08 |
02/22/05 |
- Fixed a problem with Arabic conversion, the conversion didn’t work correctly
and returned wrong characters from the replication.
- For iSeries/AS400 source databases used in mirroring or synchronization,
made a change to avoid generation of temporary files in the DBRS library.
To support this change, each DBMoto process (where there are multiple DB Moto
installations on a system) needs to be identified using a separate number. Go
to the Options dialog General tab. Click Advanced and enter a value in the DBMoto
process ID field.
|
| 4.01.07 |
01/13/05 |
Common:
- Fixed a problem that occurred with Oracle when loading the redo log files.
In some cases one group could contain more than one file member. The fix ensures
that DBMoto will load only one file member per group.
- Fixed a problem that occurred with Oracle when calculating the log entry
based on a specified date. In some cases the log history would be empty resulting
in an unexpected error in the Enterprise Manager.
Enterprise Manager:
- Modified behavior when creating a target table on Microsoft Access
to skip the check on the size of numeric datatypes because it generated
unnecessary warnings.
- Fixed a problem with the CCSID setting. When adding a new source
connection (both using the dialog or the wizard) for iSeries/AS400, the
value was always set to 37.
Data Replicator:
- Fixed a problem where, in recovery, when using DB2 UDB or DB2 MVS as
a target DBMS, some errors were not recognized as system failover and not
managed properly in the recovery algorithm of DBMoto.
- In case of AS400 as source, to log every record in the journal for a
greater degree of analysis on the error.
- Improved the tracing function when using iSeries/AS400 as a source for
mirroring replications. When more than one journal used QTEMP, the resulting
data loaded from the journal receiver in the temporary tables would be erroneous,
resulting in an incorrect journal ID saved in the metadata.
- Fixed a date conversion problem on Windows systems with locale settings
that do not use the symbol '.' as decimal separator (like Italian, German,
etc.).
- Fixed a date conversion problem when using iSeries/AS400 as a source and a
double byte CCSID in the connection properties. When the table had datetime, date
or timestamp fields, the conversion from the binary data extracted from the journal
could be erroneous.
- Fixed a problem that occurred when using Oracle: in some cases when an Oracle
source was shut down, the current transaction was not completely analyzed but the
mirroring process would skip it and restart, at the recovery of the connection,
from the next transaction.
|
| 4.01.06 |
07/12/04 |
Common:
- Fixed some errors when using DB2 UDB as a target;
- Added support for DB2 UDB as metadata with the use of HiT OLEDB
Provider for DB2 and DB2 UDB version 8.1 or greater;
- Fixed a problem when using ADO recordset objects. Calling the
Close method with some OLEDB providers would not disallocate the
object from memory or release the resources used by that object,
causing errors when reusing the same variables in DBMoto code.
Inserted code to destroy the recordset after using it;
- Added support for Gupta SQLBase as metadata and target database;
- Fixed a problem with BIGINT datatypes. With SQL Server version
7, this datatype was not supported, generating an error in
creating/upgrading metadata.
Enterprise Manager:
- Introduced more detailed information in the trace file when
running the Enterprise Manager in debug mode;
- Avoided a run-time error when connecting to a metadata database
using the wrong CCSID. Now the error is trapped and shown in the
proper dialog;
- Fixed an error when showing the ordinal position of columns
in a table (right panel in DBMoto Enterprise Manager main window),
if the ordinal was greater than 2 digits the first digit was not
shown;
- Fixed a problem in the ‘Define Publication’ dialog for a SQL
Server source database. When adding a publication, DBMoto would
try to add also the already added articles, generating an error.
The same error was generated when using the Replication Wizard
while defining a mirroring from a SQL Serve source table;
- Modified the command timeout when using the dialog ‘Execute
SQL Statement’. The command timeout was fixed to 30 seconds,
causing some queries not to be executed since they took longer.
It has now been set to the connection timeout value, assigned in
the Options dialog as ‘Source Connection Timeout’ or ‘Target
Connection Timeout’;
- Included column description information in the view dialogs
for iSeries/AS400 and SQL Server source or target databases;
- Included table description information in the ‘Table Properties’
dialog for iSeries/AS400 and SQL Server when iSeries/AS400 is the
source database and SQL Server is the target database;
- Introduced a checkbox in the Advanced Options to enable/disable
column description information. (When creating the target table,
column description information is generated for iSeries/AS400 or
SQL Server as source, SQL Server as target.)
Data Replicator:
- Fixed an error when converting CCSID 65535. iSeries/AS400
fields of type ‘H – hexadecimal’ were not considered as
alphanumeric fields and so not converted correctly;
- Fixed a problem where, in refresh mode (only in the not
optimized algorithm) when handling date/time conversion
errors, some date/time fields were not recognized as such
and so not managed according to the date conversion settings;
- Fixed a problem when inserting a new record. In some cases
eventual errors generated were not notified in the log file;
- Introduced a workaround for the sporadic error “Cannot
run DBRSJ”, usually generated after several hours of replication
using the iSeries/AS400 as a source. In case of error, DBMoto
now resets the connection to the iSeries/AS400 in order
to restore the correct replication status;
- Fixed an error using SQL Server 7 as source: Error Cannot
retrieve transactions from distribution database. (-2147217900)
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect
syntax near ':'.| The reason was that SQL Server 7 doesn’t
support advanced log functions, and that is why the ‘@’
fields will not be defined in this case;
- Enhanced support for LOB fields. In some cases, the replication
of LOB fields was not allowed even in refresh. Updated DBMoto
in order to allow LOBs to be replicated in refresh mode;
- Improved initial loading function. When loading information on the
iSeries/AS400 source tables, some table structures were loaded in memory
even if they were not replicating any data. (the user would see some warning
messages on tables not involved at all in the replication);
- Inserted a debug function to print the content of the source database
logs into the trace file during mirroring or synchronization replications.
|
| 4.01.05 |
04/02/04 |
Common:
- Fixed DBRS4JI problem related to DBRS library for iSeries/AS400: using
QTEMP support a DBRSTFL not found error was produced since DBRS4JI program
was set to produce DBRSTFL in DBRS library and not in QTEMP. Changed DBRS
library version from 4.1.0 to 4.2.0.;
- Fixed a problem for iSeries/AS400 connections, when using a Host Code
Page that is different from the target CCSID. The problem appeared as
“Run-time error '3265': Item cannot be found in the collection corresponding
to the requested name or ordinal” when starting the Data Replicator and
using any VBScript: without a VBScript, the problem was not present;
- Added support for DB2 MVS-OS/390-z/OS as target database;
- Added support for Gupta SQLBase as metadata and target database;
- In the metadata tables, reduced the size of some fields that contain
library names/ database names/table names, because in some cases the primary
key value was too long for some DBMSs;
- Increased the size for the Distributor Password field when setting a SQL
Server source connection (It was 15 characters, but now up to 35 characters
are allowed).
Enterprise Manager:
- Fixed an error when right-clicking on an iSeries/AS400 source node
and selecting ‘Version’ if the QTEMP mode was enabled;
- Fixed a problem in the ‘Select table’ dialog (and the corresponding
tab in the Source Connection wizard). The ‘Hide System Table’ checkbox
didn’t work properly;
- When opening the ‘Publication’ dialog on a SQL Server source database
node, fixed a runtime error if any of the table names were defined using
only numeric digits;
- On SQL Server source nodes, fixed a problem when creating/deleting/altering
a table. The new table structure was not correctly refreshed on the DBMoto
Enterprise Manager.
Data Replicator:
- When accessing the journal information on the iSeries/AS400, in
some cases DBMoto would get an error in the middle of the process and
continue trying to access the journal information, resulting in an
overhead in the replication process and a generation of errors in the
log. Now once there are errors during the process, the entire replication
is skipped to the next interval;
- Fixed a problem with the recovery. In some cases, when an operation
failed ,DBMoto would close and reopen the connection to the database, losing
all temporary tables and preventing correct recovery;
- Handled chained rows in replication from Oracle (when the SQL
statement is too long, Oracle stores the information in the log using
multiple records).
|
| 4.01.04 |
03/02/04 |
Common:
- Made accessible the USER name author of the transaction as a log field
(@ field) for SQL Server and AS400 (Oracle had it already). Through these
values, a replication script can be defined to make a decision process based
on the user. Specifically, a script to break the synchronization loop can be
defined giving to one of the two servers priority in case of conflict.
- Improved the quality of the DBMoto icon.
Enterprise Manager:
- Fixed an error when refreshing an AS400 source library
and no tables were found in the library.
- Fixed an error on the Create Target Table dialog when
right-clicking outside of the grid area.
- Fixed an error when editing connection parameters in a
SQL Server target connection.
- Inserted a ‘Test Email’ command button in the Options dialog
under Mail tab.
- Fixed an error when right-clicking and selecting a menu item
on a source AS400 or Oracle table from the tree view.
Data Replicator:
- In Refresh, when creating the command object on the target
connection to execute the inserts, the CommandTimeout value
has been defined equal to the Target Connection Timeout.
- In the DBRS script class, added a DBMetadata object (type:
IDatabase) accessible via script to handle the metadata
connection.
- When AS400 is a source, added a new journal field, accessible
via script and also through the Mapping Fields dialog, called
@JOUSPF (type: alphanumeric; size: 10). It contains the
user profile used for the AS400 connection.
- When SQL Server is a source, added three new transaction
log fields accessible via script and also through the Mapping
Fields dialog, called respectively: @CurrentLSN ( type:
varchar; size: 50) containing the current sequence number
in the transaction log, @UserName ( type: varchar; size:
50) containing the user name that executed the transaction
and @BeginTime ( type: datetime) containing the timestamp
when the transaction was committed.
- Fixed an error when replicating (mirroring) from AS400.
In some cases (when the receiver processed by DBMoto is
not the same as the current one), the DBMoto icon showed
an inaccurate progress percentage.
- Introduced a workaround when the following error occurs:
Unable to open DBRSTFL (-2147217900) One or more errors
occurred during processing of command.|. Some objects
appear to be locked, causing all the subsequent calls to
the DBRSJI to fail. The workaround closes and reopens the
connection with the AS400.
- Exposed to the script class the DBRS methods BeginTrans, CommitTrans
and RollbackTrans of the ADO connection object, through the DBMoto
IDatabase object.
DBMoto COM Server:
- Modified all APIs using Variant parameters to be callable via VBScript.
- Expanded the dbmReturnCode enumerated type with a new element,
dbmRetErrWriteMetadata = -4, indicating an error while writing into
the metadata.
- Added a new API, SetAS400JournalSequence to save a specified journal
receiver and sequence into the metadata.
- Added a new API, SetSQLTransactionLogSequence, to save a specified
transaction ID for a given database into the metadata.
- Added a new API, ChangeReplicationStatus, to change the replication
status for a specified table already in replication.
- Added two APIs, StartService and StopService, to start and stop the
DBMoto Data Replicator service programmatically.
Setup:
- DBMoto service is stopped before uninstalling.
|
| 4.01.03 |
02/06/04 |
Common:
- Improved error message when the help file is not found or the context
help doesn’t find the right map ID.
- Changed name to the script event 'RecordDelete_onBeforeDelete'
into 'RecordDelete_onBeforeSearch' because it actually happens
before the Search function. The 'onBeforeDelete' function
will be supported until JUNE 2005.
- Introduced the new component DBMotoSRV, a COM server
that makes available some functions defined in DBMoto to
be called programmatically. See help docs for details.
- Fixed the limitation on AS400 Log/Journal sequence number
that was 4-byte integer (limit <= 2147483647). Introduced
overflow notification when the journal is over the limit.
- Fixed the limitation on Oracle Redo Log SCN that was 4-byte
integer (limit <= 2147483647). Introduced overflow notification when
the SCN is over the limit.
- Recognized support for DB2 on Linux, Unix and OS/2 as target.
Before, only DB2 on NT was recognized.
Enterprise Manager:
- Fixed a problem when creating a target table from AS/400
to SQL Server. An alphanumeric field was always mapped to
a ‘varchar’, and not to a ‘char’ according to the ‘Variable
length’ property.
- Fixed a problem when creating a target table in the AS/400,
the BINARY and VARBINARY datatypes were inserted.
- Fixed a problem when creating a target table on the AS/400
from SQL Server. A SQL Server ‘timestamp’ field was incorrectly
mapped to an AS/400 ‘TIMESTAMP’ field (instead of using
VARCHAR), a SQL Server ‘datetime’ to an AS/400 ‘DATE’ (instead
of using a ‘TIMESTAMP’), a SQL Server ‘bit’ to an AS400
‘VARCHAR’ (instead of using a ‘SMALLINT’).
- Defined the ‘Execute SQL command…’ dialog as a modeless
dialog. Now more than one dialog can be opened and minimized
while working in the interface.
- Fixed a problem when running the replication wizard. In
some cases the icons on the treeview where not updated correctly
to indicate a replication on the specific table.
- Modified Options dialog to add a database specific dialog.
- Modified the create target table operation. From the dialog
was not possible to change table name.
- Modified the create target table operation. On some databases
the DECIMAL and NUMERIC precision and scale were not correctly
computed.
- In the Options dialog, under Scheduled Tasks tab, a scheduled
task is shown even if it doesn't contain 'DBMotoDR' as part
of the command line (but it has to be created from the DBMoto
interface to be visible).
- Fixed a problem when running the EM with the -O option.
The application didn't start correctly with the 'getting
started' wizard.
- When using Oracle as a source, the function to calculate
the last redo log SCN and the SCN from a given date have
been optimized.
- Fixed a problem in the Replication Wizard. When setting a
replication in synchronization mode, the icons on the tree-view
were not updated properly.
- Introduced DBRS library configurable via options Now it
is not necessary to set Libraries=DBRS when adding a new AS/400
source.
- Modified the Journal read point dialog. When reading the
last journal ID (and the journal ID on a given date), if an error
is generated a message is shown.
- Introduced 'Don't record failover' option, to avoid logging in
the DBMoto log all failover messages.
Data Replicator:
- Introduced static cursors for SQL Server and Oracle as
sources when running a refresh. The transactions (inserts)
run during a refresh were replicated also in the mirroring
phase, generating duplicate key errors in the log.
- Fixed a problem when the Data Replicator was stopped or
closed. Some errors on updating the metadata were generated
after the exit message because some operations were still
in execution.
- Fixed an error when the checkbox ‘CCSID 65535 conversion’
was enabled: the refresh was not converting correctly the
data from the source table.
- Fixed a problem with log management: when setting the
log management to ‘Change log file very nn days’, the option
wasn’t correctly creating a new log file when necessary.
- Removed singleton update option as introduced in the
4.1.0.1.
- Updated the component to manage DBMoto as a service (NTSVC.ocx):
the dependencies were not correctly set to the local SQL
Server causing the DBMoto service not to wait for SQL Server
to start.
- When installing DBMoto as service, introduced a new dialog
to set the dependencies to any DBMSs and changed the menu
tokens.
- Added Resynch script function under DBRS class to resynchronize
with the last transaction id (works for any source database).
- When DBMoto Data Replicator is run, a check has been inserted
if it is already running as a service.
- On refresh, fixed an error when opening source record,
if the recordset is not available we don't run the record
count.
- Fixed overflow error, mirroring from AS/400 in some cases
generated an error in reading the transactions, causing
the journal ID on the metadata to be reset to 0 and in some
cases throwing an ‘overflow’ error.
- Fixed percent value in the moving icon when in mirroring from
SQL Server and Oracle.
- Fixed a replication error when refreshing a table having any
fields not mapped at destination. The error message stated that some
parameter values are missing.
- Inserted more explanatory info on record update error messages in
DBMoto log. Now the message contains the primary key values of the source
record or all column values in case the table has no primary keys.
- Fixed a problem when changing the SQL Server subscription expiration
time (to avoid the ‘'%s' database transactions have been deleted’ error).
If set to ‘Subscriptions never expire’ the data replicator wasn’t able to
behave properly with the new setting.
- Extended the DBMoto log messages on errors when running operations on
the AS/400.
- Adjusted the recovery function when replicating from SQL Server and Oracle.
When the connection went down, the recovery wasn’t able to reopen the connection
to the server, and the entire replication from that server was disabled.
Change Journal Receiver:
- Added -D option to delete receivers (-C will just change receivers but will keep
the old ones).
|
| 4.00.21 |
11/14/03 |
Common:
- Introduced QTEMP support to run multiple DBMoto instances
on the same AS400/iSeries as a source;
- Inserted a new feature for date conversion. Some date
fields can contain values at the source server that are
not allowed in the target server or in the Windows system
itself. It is possible to set these fields to Null value,
or a specific date value, or to raise the error;
- Added DEBUG feature to collect trace information during
the execution of the application;
- Improved string management for performance;
- Fixed an error on Oracle when adding log files to open
the log miner;
- Fixed a bug in SQL Server source using ODBC, the name
of the SQL Server was not detected correctly. The error
was: "Cannot connect to Server 'Server name' (Automation
Error).;
- When using SQL Server as metadata, with a case sensitive
collation, errors were generated when opening metadata tables;
Enterprise Manager:
- Improved the behavior of the Apply button
in various forms;
- Inserted a warning if using the script object SourceRecordBefore
on sources not AS/400;
- In the Journal Read Point dialog, set the
initial date of the Date control to the actual
date;
- Wizard Replication and Wizard Creation Table, fixed an
error when going back and forth with the object selection
tabs, the combobox listing connections, databases/libraries/schemas
and tables were not correctly updated;
- On a SQL Server source node now it is possible to read
and modify the connection properties. The old connection
properties (that were more precisely system properties)
have been put under a different menu item;
- Fixed the error handling procedure when opening the standard
OLEDB dialog for editing the connection string;
- Fixed an error in the toolbox, getting information on
a source SQL Server node;
- Fixed a problem when inserting the product key in the
Wizard, when spaces where left on the code field;
- Fixed: In dialog Creation Table, when MSAccess is selected
as target database, the size of the columns was not correctly
calculated;
- Added a check in Creation Table dialog: when running the
creation script, if trying to select a target connection
that is a different database from the one selected in the
main dialog;
- Inserted an Execute SQL command dialog on
all source and target nodes;
- When inserting a new metadata/source/target connection,
the connection name was not trimmed, causing in some cases
errors in reading the db objects under that connection;
- Fixed a bug in Select Tables dialog, when
selecting multiple tables to add, the previous tables were
deselected;
- Added menu items under Help to open the URL
for the Online Help and the Knowledge Base;
- Fixed an error when refreshing source tables lists,
tables physically deleted from the database were showed
as still existing;
- Added support for the bigint datatype in Create Target
Table;
- Fixed an error in Create Target Table: Error occured when
converting smalldatetime datatypes from Microsoft SQL Server
to Microsoft Access.
Data Replicator:
- Fixed a bug during refresh, in case of an error reading
a source field, the log file wrote TOKEN_NOT_FOUND instead
of the correct field name;
- In refresh, in the main loop, in case of errors reading
the source fields the variable assigned to the internal
field structure was not set to Nothing causing the next
field to point to the previous one;
- During replication from AS400, if the receiver used was
an old (detached) receiver, the number of transactions returned
was wrongly calculated, causing loss of transactions;
- In replication from Oracle, introduced the COMMITTED_DATA_ONLY
option to avoid the need to create and map the ROWID column
(only on version 9.2 or above);
- Fixed a bug with metadata in MySQL, the SQL syntax used
was not supported causing an error when starting the replicator;
- Added refresh of option settings for every refresh interval
time;
- Fixed a bug when replicating in Continuous Refresh mode,
when checking and calculating the next refresh time;
- Fixed a bug in refresh, the command was not always closed
properly;
- Fixed an error in miscalculating the sign for packed numbers
in AS/400 source.
- Changed the scope of some properties/methods in DBRS Class;
- Fixed a run-time error in starting the data replicator
when running the DR in debug mode;
- Fixed a bug in the upgrade from DB2Motion to DBMoto causing
source connections to SQL Server throwing the error: Error
Server '' is not enabled to publish on server <server
name> when data replicator is running.
Setup:
- Removed PDF files from Setup.
Change Journal Receiver:
- Fixed an error: When starting the CHGJRNRCV, the application
was not aligned with the new version of metadata. The connection
string from the AS/400 sources was not correctly read and
the application would run idle.
|
| 4.00.12 |
09/25/03 |
Enterprise
Manager:
- Microsoft Access: Dropped use of datatype TINYINT in table
creation because not supported from MSAccess;
- Show Table function: Improved performance by using an
optimised grid to show data and introduced the Get
Next Rows menu item to scroll through the entire recordset;
- Fixed a regression bug in the EM introduced in the 4.0.11,
when exploring the database node under a SQL Server source;
- Journal management: Enhanced the Journal Read Point
dialog by using new controls for the date and time.
|
| 4.00.11 |
09/19/03 |
Common:
- Introduced support for target and metadata recovery;
- Target recovery: Introduced two recovery features, choice
between stopping the failed replication or keep pinging
the target server;
- Source and target recovery: Introduced the option to send
a notification email to the system administrator in case
of failure;
- In Oracle redo log reading: Inserted a filter to analyse
log files not in an archived status.
Enterprise Manager:
- Toolbox: The source connection properties were actually
listing metadata properties;
- Scheduler: The command line was not editable;
- Introduced a search feature in the Select Tables
dialog, now its possible to use the typing completion
to find a library/database or a table in the treeview. Use
SPACE or RETURN to check/uncheck a single table;
- Fixed a bug in Table mapping dialog when setting replication
status to 2 Continuous Refresh, in calculating
the next refresh time;
- Fixed an error at the end of the Target Connection Wizard,
if choosing to proceed to define a replication;
- Fixed an error in the Create Target Table Wizard, if choosing
to continue with the Replication Wizard, the Create Target
Table wizard would be opened again;
- On AS/400 and Oracle sources, when all tables under a
library/schema are deleted, also the library/schema is deleted
from the treeview;
- Fixed an error in Redo Log dialog when inserting NULL
in the Sequence Number field and save it;
- Fixed a problem when listing objects with a numeric name
(databases, libraries, schemas, tables) in the wizards.
Data Replicator:
- Log management, fixed a runtime error when the log file
did not exist;
- Introduced RRN handling for AS400 target tables with no
primary keys;
- Changed connection handling, now only source/target connections
having at least one table in replication (status different
from 3 Replication Finished) are opened
when running the Data Replicator.
|
| 4.00.9 |
08/25/03 |
Enterprise
Manager:
- Fixed an error in metadata creation when using Microsoft
Access.
- Fixed problem with Sybase: The OLEDB Provider for Sybase
was not recognized;
- Fixed a bug in Field Mapping dialog: a runtime error appeared
whenever columns weren't found in the table;
- Fixed an error in MySQL as metadata: The SQL syntax was
not accepted;
- Fixed an error in Log management that occured when set
to Change every N days;
- Fixed a problem in Setup: When installing the ODBC driver,
the driver was installed correctly but some registry entries
were missing.
|
| 4.00.7 |
08/11/03 |
Enterprise Manager:
- Performance enhanced via Windows ADO architecture support;
- Support for multiple client DBMoto instances;
- Support for Sybase as target and metadata;
- Support for Microsoft Access as target and metadata;
- Support for DB2 UDB as target and metadata;
- Support for MySQL v4 as target and metadata;
- Metadata Connection Wizard: Automates the process of connecting
to the Metadata database;
- Source Connection Wizard: Automates the process of connecting
to the Source database;
- Target Connection Wizard: Automates the process of connecting
to the Target database;
- Replication Wizard: Automates the Replication process.
Set Replication Mode and Status, set Refresh interval, set
Mapping Rules, all at once;
- Drag and Drop Functionality for creating Target tables
and replicating Source tables: Simply selecting a Source
table and dragging it to the Target menu activates the Replication
Wizard;
- Create Target Table Wizard: Guides process of selecting
Source library;
- Source table, Target database, Target table, viewing the
table structure generated from the Source table, and reviewing
the table creation script generated by the Wizard;
- VBScript Email Functionality: Enables the user to send
an email using the VBscript modules;
- Improved the Journals Management: read and update multiple
journals;
- The DBMoto Toolbox: Lets you view replication metadata,
Source and Target database details;
- Scheduler: Schedule Replication Start and Stop, automates
Windows Scheduled Tasks (tm).
Data Replicator:
- Performance enhanced via Windows ADO architecture support;
- Support for multiple client DBMoto instances;
- Support for Sybase as target and metadata;
- Support for Microsoft Access as target and metadata;
- Support for DB2 UDB as target and metadata;
- Support for MySQL v4 as target and metadata;
- Status Notification: Icon on the Windows Task Manager
bar displays that a replication is in progress and also
indicates the percentage of records replicated;
- Log Management: Determine the dates/times desired to update
or generate the log file. Configurable size.
Change Journal Receiver:
- Performance enhanced via Windows ADO architecture support.
Journal Manager:
- New tool automates the process of creating and managing
AS/400 journals and libraries.
|
| 3.10.7 |
06/10/03 |
Enterprise
Manager:
- Fixed a problem with time separators in the Journal Synchronization
dialog: Some language settings (ex.: German) didnt
accept the . as a time separator.
Data Replicator:
- Fixed an error in the Oracle parser: Table names and library
names without double quotes where misinterpreted in reading
the log miner.
|
| 3.10.6 |
06/03/03 |
Enterprise Manager:
- Added: New DBRS savefile DB2M400.svf to resolve timeout
errors when trying to add libraries and tables in the DB2Motion
E.M.; DBRS files are now created with a default CCSID=37
(US English) and not 280 (Italian), which caused problems
on OS/400 systems not supporting 280.
|
3.10.5
|
05/19/03 |
Enterprise Manager:
- Added field types for AS/400 source table;
- Improved field conversions during Create Target Table;
- Added new field types to Create Target Table dialog;
- Fixed a bug on Retrieve Last Transaction ID in SQL Server
transaction log window;
- Fixed a bug with ODBC Direct when retrieving target tables
list;
- Fixed a bug in ShowTable Window: there was an error reading
the first field of the table;
- Fixed a bug in ShowTable Window when reading from Oracle
(now uses Dynamic cursor to open the table);
- Introduced a check when adding a new source AS/400, the
DBRS library must be explicitly linked as a connection string
parameter;
- Fixed: DB2Motion now uses QTEMP (for multiple DB2Motion
instances running on the same AS/400 and no more problems
on DBRSTJ) to access AS/400.
Data Replicator:
- Fixed a bug on source SQL Server when multiple target
tables were replicated from a single big record size table;
- Added new optional parameters for the AddLog method;
- Added a new property to SourceRecord classes which returns
RecordsAffected;
- Added two new events on Transactions Read for a table;
- Fixed: Target recordsets now close after Oracle RedoLog
analysis;
- Added a new DBSource property to the DBRS class (similar
to DBTarget);
- Added two new properties to the DBRS SourceDSN and TargetDSN
classes (similar to DSN but one works on a source database
and the other works on a target database). DSN has been
kept for backward compatibility with VBScript (TargetDSN
is equal to DSN);
- Added two new methods to SourceLookUp and TargetLookUp
DBRS classes (both similar to LookUp but one works on a
source database and the other works on a target database).
LookUp has been kept for backward compatibility with VBScript
(TargetLookUp is equal to LookUp);
- Added check for LOB fields. Since LOB fields are currently
not read from a source database, DB2Motion does not hang
and it prints only one error on the log;
- Added error checking during fields value read. Prior
to this, DB2Motion would hang, now it prints an error in
the log file;
- Added target database type checking before trying to truncate
the target table;
- Fixed a bug that occured when the source fields in SQL
Server were Null;
- Added Str function to VBScript (the behavior is the same
as the VB function, be careful about leading spaces when
there are positive numbers);
- Fixed a bug that occured when reading metadata information
(columns, indexes, primary keys) in numbers > 50;
- Disabled script timeout for the VBScript functions (no
timeout limit on script execution);
- Fixed: DB2Motion now uses QTEMP (for multiple DB2Motion
instances running on the same AS/400 and no more problems
on DBRSTJ) to access AS/400.
Change Journal Receiver:
- Enhanced journal tracking algorithm.
|
3.10.4
|
02/05/03 |
- Raised timeout for Oracle connection to redo logs;
- Fixed an error in Enterprise Manager when listing columns
from an Oracle table and the UID in the connection was lower
case;
- Fixed an error running an update on the metadata with
Oracle as metadata database;
- Fixed an error on metadata statements with Oracle as metadata
database, during the source table refresh;
- Fixed an error in opening the Mapping dialog on an Oracle
table when same table exists in another schema;
- Fixed an error on refresh Oracle fields on replication;
- Fixed a run-time error in opening the Redo Log dialog;
- Introduced double byte languages support;
- Introduced Arabic language support;
- Fixed an error during replication of NULL values where
target field was updated with string 'NULL' rather than
hex 00.
|
| 3.00.3 |
11/22/02 |
- Added base support for Oracle 8i and 9i as source;
- Fixed a bug on long record length with AS/400 as source
(JOESD size is now calculated by DB2Motion);
- Fixed a bug for AS/400 dates with year<100;
- Fixed a bug on source SQL Server databases where the target
table replication mode is Refresh or Continuous Refresh;
- Added support for record lengths greater than 1024 on
AS/400;
- Fixed the timeout during access to target system tables;
- Changed table names in query from lower case to upper
case;
- Increased timeout to 120sec for all connections;
- Fixed parsing problem in SQL->AS/400 replication.
|
|
2.54.1
|
09/19/02 |
- Added support for date and time formats on AS/400.
|
| 2.54.0 |
09/01/02 |
User Interface:
- Added basic support for MySQL as Target Database;
- Added support for MySQL as Metadata Database;
- Shortened Sourcefile and Sourcefield fields from 250 to
200 to support MySQL;
- Fixed bug regarding Oracle's recognition of ODBCDirect
Connection;
- Modified the string table and password encryption method;
- Fixed a problem in connecting the publisher to the distributor;
- Added CCSID 65535 support;
- HiT ODBC Server/400 for DB2Motion now can be used via
ODBC TEST;
- EBCDIC Cyrillic support (1025) is now available along
with HSTABLE.
Data Replicator:
- Added basic support for MySQL as Target Database;
- Modified Data Replicator to use ODBCDirect;
- Added ")" to the list of separators for the
SQL Parser;
- Modified the string table and password encryption method;
- Added the II f function to VBScript;
- Fixed a bug where in certain cases the onAfterPKRetrive
function wasn't called;
- Added CCSID 65535 support;
- Modified the DB2Motion startup to shorten response time.
|
| 2.53.1 |
08/26/02 |
Data Replicator:
- Modified the string table and password encryption method;
- On Startup, a check is performed to find out if another
instance of DB2Motion is already running;
- Three attempts are now made before canceling a receiver.
|
| 2.51.0 |
06/28/02 |
- Added a form to see table content (records);
- During table creation last database type selected is saved
and restored between sessions;
- Fixed metadata to allow SQL Server database names longer
than 10 characters. There is not an automatic conversion
(see KB);
- Fixed the Transaction ID read in case the transaction
log is empty;
- Added Val function to VBScript. It does not use the regional
settings;
- Added journal start/stop check on a replicated table;
- Minor bug fixes in main Enterprise Manager window;
- Minor bug fixes in Table Creation window;
- Minor bug fixes in Table Replication window;
- HiT ODBC/400 now recognizes the new DB2MOTIONJOURNALDIAG
utility;
- HiT ODBC/400: Modified optimistic approach support for
positional queries (i.e. DAO) to handle case sensitive field
names;
- Fixed a bug in showing error in CRecord Class.
|
| 2.50.0 |
05/15/02 |
- Increased maximum size of *char fields on SQL Server;
- Increased the maximum timeout value in source connections;
- Changed encryption system to support DB2 metadata;
- Enabled SQL Server replication;
- Enhanced primary key error handling on target tables;
- Enabled service stop during full refresh;
- Enhanced Oracle and case sensitivity support.
|
|
2.1.0.6
|
05/06/02
|
- Fixed bugs in DB2/400 tables with names containing double
quotes;
- HiT ODBC/400 now sets the DATABASE token in the output
connection string and recognizes the new CHGJRNRCV.EXE utility;
- Added possibility to create metadata on DB2/400;·
Minor bug fix: Data Replicator does not hang if a target
field is deleted from the target table;
- Eliminated the trailing spaces deletion during refresh
phase. (This solves cast errors on SQL Server and other
problems when the primary key fields contains only spaces);
- Fixed data Replicator user interface when right-clicking
the tray icon. Now when left-clicking outside the menu,
the menu is closed;
- Added language files version checking;
- Changed the log output of the character maps reader.
|
|
2.1.0.4
|
04/15/02
|
- Now able to update the license key by user interface;
- Minor bug fix: improved case sensitivity in the list views;
- Removed the SQL Server's Automatic Refresh: slowing down
application too much;
- Corrected some messages and display strings;
- Fixed bug on SQL Server sources: This bug occured during
the first Transaction ID reading;
- Fixed bug in the password encryption process: Could not
decrypt password and the SQL Server source connection without
the trusted connections;
- Minor bug fix on errors display class (CSourceDSN);
- Eliminated problem: When accessing the Journals form,
the error showed up as "Item not found in this collection".
|
|
2.1.0.3
|
4/5/02
|
- Fixed Delete button bug in the FrmCreaTabellaSQL form;
- Implemented the reading of the Time (T) type fields on
the AS/400;· Corrected some strings;
- Corrected the creation system tables for when the AS/400
is the target.
|
|
2.1.0.2
|
02/25/02
|
- Increased the DB2 fields' maximum length when mapping
fields ranging from 10 to 250;
- Ordered the tree-view that displays the SQLServer tables.
- Fixed bug on the "Create Table": If the DSN
is non-existent the program stops;
- Fixed bug on AbortRecord in the update UB and BR records.
|
|
2.1.0.1
|
03/06/02
|
- Added SQLServer source support;
- Fixed bug on mapping table finalization: If the table
is mapped it becomes highlighted, while the other tables
are grayed, in the tree-view. This influences the fields
display as well.
- Added management of various new methods to DBRS class
in order to have more control over the data replication
process.
|
|
2.1.0.0
|
03/01/02
|
- Fixed a bug in the query to order by a journal's date
sequence: it did not work in systems with various date formats.
|
|
2.0.0.4
|
01/25/02
|
- Fixed Bug where the link in the Start menu would call
up DB2Motion AS/400 instead of DB2Motion Enterprise Manager.
- Fixed problem: ODBC driver now installs correctly;
- Fixed the FileSystemBrowser, now installs and registers
correctly;
- Fixed problem concerning the radio buttons during Uninstallation.
|
|
2.0.0.2
|
12/20/01
|
- Checks for UP records. If no UB record is found, DB2MotionDR
sends a warning. This happens if the journal is not set
to *BOTH;
- Bug fix - database type recognition (now recognizes Oracle
better);
- Major changes on primary keys retrieved from Oracle (no
more tabledef access needed). Primary keys now have to be
defined as constraints (not just unique indexes).
- Minor Bug fix on SQLServer/Oracle table generation setup;
- Oracle table generation - schema is now the default user
schema;
- Major changes in Oracle table retriever. Oracle tables
are now retrieved from the default user schema;
- Major bug fixes in Oracle tables access. Tables are now
listed without tabledef access;· Improved speed on
Oracle access.
|
|
2.0.0.1
|
12/10/01
|
- Bug fix - Better transaction handling on the AS/400;
- Improved database type recognition (older version sometimes
recognizes Oracle because of 'strange' ODBC error);
- Bug fix on SQL Server/Oracle table generation. The packed
field size is now buffer * 2;
- Bug fix on main screen. In the AS/400 fields list, the
packed field size is now buffer * 2.
|
|  |