[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference orarep::nomahs::dbintegrator_public_public

Title:DB Integrator Public Conference
Notice:Database Integration - today! Kit/Doc info see note 36
Moderator:BROKE::ABUGOV
Created:Mon Sep 21 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1171
Total number of notes:5187

1071.0. "%RDB-E-INVALID_BLR error during a replication transfer from RDB to ORACLE" by ORAREP::LEMAN::NAUFFRAY () Thu Jun 20 1996 10:31

Hi,

   Even after installing the last DDD 6.0 official version, I still have the
folllowing failure :


%DDAL-E-ERRACCDSTDB, error occurred accessing the destination database
-DDAL-E-SUPP, %RDB-E-INVALID_BLR, request BLR is incorrect at offset 101
-DDAL-E-SUPP, -DBI-I-CTXVAR_EXISTS, Context variable 0 previously declared at
 BLR offset 191


when trying to operate a replication transfer from RDB to Oracle in this
context :


	- Source database machine VAX/VMS V6.1 hosting RDB
	- Target database machine INTEL/NT     hosting Oracle7 Server 7.1.3.2.0 
	- DBI gateway for Oracle V3.1-02A working with SQLNET 1.2 client on VMS
	- DDD V6.0

	- The access to Oracle database through  SQL/RDB  works fine.
	- The access to Oracle database through the DBI GTW ORACLE works fine.
	- The Initial Replication transfert works fine.

   But :
	- The Update Replication transfert fails at BLR errors.

        That means only extraction transfers are able to work in this context,
        but not replication transfers.


  The last answer given about this problem was in the note Number 202.1      
in the DATA_DISTRIBUTOR conference, and advised to install the last DDD 6.0
official version to solve the problem.

  I installed the preconised version (VMS distrib. December 95), but it's still
failing.

  Is there a patch to apply or a workaround existing ???

  Thanks for the answer to this issue to be solved urgently.
  
  James
T.RTitleUserPersonal
Name
DateLines
1071.1Follow this in the DDD Notes ConferenceBROKE::PROTEAUJean-Claude ProteauThu Jun 20 1996 10:579
    James,
    
    Your problem sounds identical to one which was solved sometime ago, and
    for which the correction ought to exist in the latest DDAL kit
    (V6.0-11), now shipping from Oracle.  This is the kit you installed, I
    take it.  Since this is a Data Distributor problem, we'll handle it in
    your note in the DEC_DATA_DISTRIBUTOR notes conference.
    
    Claude