Conference orarep::nomahs::dec_data_distributor

    
    Bad request handle is typically an error in the software, in this case
    in Data Distributor (or possibly in Rdb).  A request handle is an
    internally-generated, short-hand method of identifying a database
    request to the datbase management system.  When a request is compiled,
    the request handle should have a null value, indicating that it is free
    to be assigned to the request being compiled.  Once the request has
    been compiled, other database requests to do something with the
    request, such as, start the request, send parameters to the request,
    receive answers back from the database system via the request, etc.
    These require a request handle to tell the database system which
    compiled request to work with.  If the error occurs then it could mean
    that the request was never compiled (a null request handle value), that
    the request was prematurely discarded (released), or that the request
    handle value has somehow been overwritten with a bad value.
    
    I suggest that the latest version of Data Distributor 6.0 be obtained
    from Oracle.  The current shipping version is V6.0-11.  If you find
    that the problem still persists, please submit a formal problem report
    through the appropriate support channel, and we'll investigate the
    reason for the failure.
    
    	Claude

    
    
    	Customer is already running 6.0, so I guess, all I need are the 
    	patches for that version.  I'm the Oracle support here in Brazil
    	(here, Oracle has an agreement with DEC so we still support all the
    	products they got from us).  What the Rdb folks usually do is that
    	they copy the pacthes over a DEC system and I copy it from there,
    	could you please do the same??
    
    
    				Thanks a lot
    
    
    					Claudia
    				

    
    Claudia,
    
    Please send our request to [email protected].  Steve is the manager
    for Data Distrutor (now being called the Rdb Replication Option).  I've
    been told that the updated version of our product is now shipping
    from Oracle.  However, I don't know how the product is made available
    to existing customers.  I've forwarded your note to Steve, but it would
    be a good idea for you to send mail to him directly.
    
    Claude

    
    Claudia,
    
    I've spoken to Regina Phelps, who handles submission of our kits for
    production.  She will send you mail explaining how you can obtain the
    latest revision of DDD 6.0.  Regina can be reached via the internet
    at [email protected].
    
    Claude

Claudia,

The revised Data Distributor 6.0 kit is located on node BROKE in our VMS
development cluster:

Directory DD$DISK:[KIT.DDAL.V60-11]

The VAX savesets:

DDAL060.A;1             414/416     17-APR-1996 15:03:35.57
DDAL060.B;1            1404/1404    17-APR-1996 15:03:39.74
DDAL060.C;1            2772/2772    17-APR-1996 15:03:50.92

The Alpha savesets:

DDALA060.A;1            414/416     17-APR-1996 15:07:05.71
DDALA060.B;1           2430/2432    17-APR-1996 15:07:09.27
DDALA060.C;1           2772/2772    17-APR-1996 15:07:23.11

Total of 6 files, 10206/10212 blocks.

If you have a way to copy these savesets from our system, fine. go ahead.
If you can't, we might have to set up a directory on some other machine
from which you can transfer via ftp.

Claude

    The RDB folks have the following area "ORAREP::ORAREP2:[RDB_V60_KIT]" 
    open for us Digital folks.  Could you put your KIT on this node so we
    can copy them. 
    
    rgds,
    james delahunty
    

    Re 216.6:
    
    James,
    
    I spoke to some of the Rdb folks.  I was told that a special program
    was set up so that Digital internal engineering groups could obtain the
    Oracle Rdb kits from the ORAREP node as you described.
    
    This same mechanism is not yet in place for the Replication Option for
    Rdb (aka Data Distributor) product.  It was suggested that you contact
    Andy Schneider at DTN 381-1696.  Andy was the person, I was told, who
    set up the program.  There may be information about it in the
    ORACLE_PROGRAM.NOTES conference on node ORAREP.  I assume Andy will
    arrange something with my manager to make our kits available in the same
    way as was done for Oracle Rdb.
    
    Claude

Claudia,

As an Oracle employee, you should be able to use FTP to copy the Replication
Option for Rdb (formerly DEC Data Distributor) savesets from any of the follow-
ing machines:  MOKLOC, DEBIT, KREDIT, SQLRUS, QUILL.  The user account FTP_KITS 
will put you in the directory where the files currently reside.

[If you are a Digital employee reading this note, you will not be able to access
the kits in this way.  These machines are not accessible from the Digital Engin-
eering network.]

The saveset files are these:

The following three files consitute the savesets for Data Distributor V6.0-11
for OpenVMS VAX:

DDAL060.A;1             414/414     17-APR-1996 15:03:35.57
DDAL060.B;1            1404/1404    17-APR-1996 15:03:39.74
DDAL060.C;1            2772/2772    17-APR-1996 15:03:50.92

The following three files consitute the savesets for Data Distributor V6.0-11
for OpenVMS Alpha (note the extra 'A' in the names):

DDALA060.A;1            414/414     17-APR-1996 15:07:05.71
DDALA060.B;1           2430/2430    17-APR-1996 15:07:09.27
DDALA060.C;1           2772/2772    17-APR-1996 15:07:23.11

- Claude

    Hello Claude,
    
    What is the decnet address of node BROKE:: within Oracle ?
    
    Thanks a lot.
    
    _Luc

    It is 43.159