| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5.1 | VAX Data Distributor V2.2 Features | BROKE::PROTEAU | Jean-Claude Proteau | Thu Mar 03 1994 19:37 | 32 |
| 5.2 | VAX Data Distributor V2.3 Features | BROKE::PROTEAU | Jean-Claude Proteau | Fri Mar 04 1994 08:28 | 94 |
| 5.3 | VAX Data Distributor V2.4 Features | BROKE::PROTEAU | Jean-Claude Proteau | Fri Mar 04 1994 08:41 | 22 |
| 5.4 | DEC Data Distributor V5.1 Features | BROKE::PROTEAU | Jean-Claude Proteau | Fri Mar 04 1994 08:47 | 25 |
| 5.5 | DEC Data Distributor V6.0 Features | BROKE::PROTEAU | Jean-Claude Proteau | Fri Mar 04 1994 09:33 | 154 |
| 5.6 | Replication Option for Rdb version 6.0-11 | BROKE::PROTEAU | Jean-Claude Proteau | Tue Aug 13 1996 11:35 | 34 |
|
Replication Option for Rdb version 6.0-11
When DEC Data Distributor was purchased by Oracle corporation from Digital
Equipment corporation, the product was re-released from Oracle and the
product name was changed to the Replication Option for Rdb.
The Oracle release is version V6.0-11. This version contains a number of
corrections to the original V6.0-0 product:
1. The transfer monitor would sometimes crash when a transfer was deleted
(infrequent problem).
2. The transfer monitor would sometimes crash when handling an extraction
rollup transfer creation. This occurred for transfers with a lot of
table definitions.
3. Replication transfers only worked if the target was an Rdb or OracleN
database.
4. Replication transfers might fail trying to drop a DDAL$DBKEY_INDEXn
target index. An unusual set of circumstances caused this problem.
5. The second execution of an extraction transfer to an existing target
database failed with an INVSYSBLOB error. The cause had to do with
a multisegment query header column attribute.
6. Transfers involving Rdb version 7.0 did not work. This was due to the
name change from DEC Rdb to Oracle Rdb.
7. Sporadically, SQL would hang waiting for a completion message from the
transfer monitor. This was due to a conflict in the way the monitor
used VMS event flags.
|
| 5.7 | Replication Option for Rdb version 7.0 | BROKE::PROTEAU | Jean-Claude Proteau | Fri Jan 10 1997 16:18 | 89 |
|
Replication Option for Rdb 7.0
Features
The following is a list of the features of version 7.0.
o Transfers into PC Databases
Support has been added for transfers from and to Microsoft ACCESS
and Microsoft SQL Server databases via the Rdb Transparent Gate-
way to PC Data.
o Transfers into UNIX Databases
Support has been added for transfers from and to Oracle Rdb databases
on Digital UNIX.
o Transfers over TCP/IP Networks
Data transfer over TCP/IP networks is now supported, as well as
data transfer within DECnet networks.
o Support for Oracle Transfer Databases
The design of the transfer database tables has changed so that
one now has the option of using either Oracle Rdb or Oracle
Rdbms (e.g., Oracle7) as the repository for the transfer
database tables.
o Support for Multiversion Rdb
It is now possible to run the Replication Option with a multi-
version variant of Rdb without changing the Rdb version in the
SYSTEM logical name table. A number of the command procedures
for the Replication Option have been modified to support this
new mode of operation.
o More Performance Enhancements and Options
A number of options have been implemented to give you more
control over the execution of transfers. Most of these options
are designed to improve product performance. Here is a brief
description of each option.
- RDB$CHANGES table separate storage area
- Index on replicated source table
Options
- Number of rows read and written at a time
- Delete and write target data in a single transaction
- Start transfer with a particular named table
- Parallel initial replication transfers
- Checkpointing enhancements
o Multiple Transfers to Same Target Tables
There now exists an option to permit shared-writing of target
tables. Several transfers can write data into the same target
table. So can user applications.
o Transfer Data Definitions Without Data
There now exists an option to transfer data definitions without
also transferring the data. This can make it easier to create
multifile target databases.
o Alternative Way to Define Options
In prior versions of the Replication Option, customization was
done by defining VMS logical names. That still can be done, but
there is now an alternative. One can create resource configura-
tion files. These are plain text files that list variable names
and their definitions.
o Messages Changed to SQLese
Messages that appear in Replication Option log files now use SQL
terminology.
o Single System Shutdown
A change has been made to the procedure used to shut down the
Replication Option. In the past, execution of this procedure
would shut down the Replication Option on all nodes in a cluster.
Now the shut down only occurs on a single node.
|