[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | The Replication Option for Rdb |
Notice: | Product renamed to Replication Option for Rdb |
Moderator: | BROKE::PROTEAU |
|
Created: | Wed Mar 02 1994 |
Last Modified: | Wed Jun 04 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 287 |
Total number of notes: | 1231 |
221.0. "Accvio, initial replication RDB v6.1 to v4.1?" by ORAREP::KERNEL::PULLEY (Three cheers for the holy spirit) Thu Jun 13 1996 11:46
Hi Folks,
Well I thought I seen this before but ...
My customer's trying to do an initial replication, from a source node
VMS v5.5-2, RDB v6.1 MV, DDD v6.0-0, to a target of VMS v5.5-2, RDB v4.1,
DDD v2.3.
It's to a new database.
He can transfer from databases the other way.
He can transfer from the source node back to it's self.
When his transfer fails, it stops with:-
%ddal-i-defgblfld, .... rdbvms$vintage_transfer_name
%system-f-accvio, reason=00 virtual address=00000008, pc=00199237, ...
I suggested trying rdb$remote_multiplex_off 1 on his source node but
he said that didn't make any difference.
Thanks for any suggestions,
Steve.
T.R | Title | User | Personal Name | Date | Lines |
---|
221.1 | Note sure what to say | BROKE::PROTEAU | Jean-Claude Proteau | Thu Jun 13 1996 12:18 | 15 |
|
Steve,
I don't recall if we've ever seen such a problem.
If the customer is able to perform one transfer from Rdb 6.1 MV to
the remote Rdb 4.1 system but not another transfer, then perhaps it is
a resource problem. Otherwise, it would seem to be an environment
definition problem or an outright bug.
The fact that the customer can perform the transfer successfully if the
target is a local disk rather than a remote one makes it seem as if the
problem is in the Rdb remote software.
Claude
|
221.2 | RDB v6.1 ECO 1 fix. | ORAREP::KERNEL::PULLEY | Three cheers for the holy spirit | Fri Jun 14 1996 06:59 | 4 |
| What I was trying to say in .0 was they weren't able to use any v4.1
targets, or v4.2 for that matter.
Anyway, they put on RDB v6.1 ECO 1, and the problem was gone.
|