Conference orarep::nomahs::dbintegrator_public_public

1168.0. "DBI create table to remote rdb - access vio" by BROKE::BITHER () Wed May 21 1997 15:25

Node USEAA2
-----------
Rdb 6.0
Rdb 7.0
DBI 7.0 (catalog is in Rdb 7.0 db)
Alpha OpenVMS 6.2-1H3
DECdtm running - log files is NOT stalled.

Node USAOS
----------
Rdb 6.0
Rdb 7.0 
Alpha OpenVMS 6.2-1H3
DECdtm running - log file is NOT stalled.

Node USDEV2
-----------
Rdb 6.0
Rdb 7.0
Alpha OpenVMS 6.2-1H3
DECdtm running - log file is NOT stalled.


PROBLEM:

DBI on node USEAA2 has links to:

   Rdb 6.0 and Rdb 7.0 udbs on node USDEV2
   Rdb 6.0 udb on node USAOS

Create tables to the udbs on node USDEV2 work fine.  Create table to the
remote database on node USAOS results in:

ATTACH 'FILE/TYPE=DBI/DBNAME=MSP_DBI';
SHOW LINKS;
User links in database with filename /TYPE=DBI/DBNAME=MSP_DBI
Link CMSP_LINK
     Connection information: USAOS::RDBBUUS$USC
     To database type: Rdb
     State: Inactive

Link MSP_LINK
     Connection information: USDEV2::MSP_US
     To database type: Rdb
     State: Inactive

SQL> create table CAPGROUP_MASTER_REL link to CAPGROUP_MASTER_REL using
CMSP_link;
%RDB-E-NO_META_UPDATE, metadata update failed
-DBI-F-IMPORT_FAIL, Import of object CAPGROUP_MASTER_REL failed.
-RDB-F-IO_ERROR, input or output error
-SYSTEM-F-LINKABORT, network partner aborted logical link
-RDB-E-DISTABORT, distributed transaction was aborted
-RDB-E-NOSECERR, cannot determine secondary error
-RDB-E-DISTABORT, distributed transaction was aborted
-RDB-E-NOSECERR, cannot determine secondary error
-RDB-E-DISTABORT, distributed transaction was aborted
SQL> exit;
There are uncommitted changes to this database.
%RDB-E-DISTABORT, distributed transaction was aborted
-RDB-E-NOSECERR, cannot determine secondary error
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=
00000000, PC
=00000000, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 00000005
                        Name   = 0000000C
                                 00010000
                                 00000000
                                 00000000
                                 0000001B

    Register dump:
    R0  = 0000000000000001  R1  = 0000000000000000  R2  = 00000000007DD5D0
    R3  = 0000000000A488F0  R4  = 00000000007FF4C0  R5  = 00000000008F2024
    R6  = 00000000000023B4  R7  = 0000000000740918  R8  = 000000000138816C
    R9  = 0000000010000000  R10 = 0000000002228D1C  R11 = 000000007FFBE3E0
    R12 = 0000000000000000  R13 = 000000007EEEE900  R14 = 0000000000000000
    R15 = 000000007EEEDDA0  R16 = 0000000000740918  R17 = 00000000008044F0
    R18 = 000000007EE2B718  R19 = 0000000000000000  R20 = 0000000004A3802A
    R21 = 0000000000000000  R22 = 0000000000000003  R23 = 0000000000000002
    R24 = FFFFFFFF82F04D98  R25 = 0000000000000003  R26 = 0000000000000000
    R27 = 00000000007D2460  R28 = 0000000000851504  R29 = 000000007EE2B740
    SP  = 000000007EE2B740  PC  = 0000000000000000  PS  = 000000000000001B

This access violation shows up in the netserver.log on the USAE22 machine
(system with DBI).  


NOTES:

1.  She is able to create links to the udb on node USAOS and commit them.
I believe this shows decdtm is running ok on both the dbi node and the
remote node.  

2.  To be sure decdtm running ok had her do:
    Check tp_server and ipcacp are running.
    lmcp>show log/current on both system.  Log file is not stalled on
either system.

3.  She is able to attach directly to the udb on the remote node when
not using dbi.

SQL> ATTACH 'FILE USAOS::RDBBUUS$USC';
SQL> SHOW VER
Current version of SQL is: Oracle Rdb SQL V7.0-0
Underlying versions are:
    Database with filename USAOS::RDBBUUS$USC
        DEC Rdb V6.0-16
        Rdb/Dispatch V6.0-26 (OpenVMS AXP)
        Remote Server V5.1-14 (OpenVMS AXP)
        Remote Client V7.0-0 (OpenVMS AXP)
        Rdb/Dispatch V7.0-0 (OpenVMS AXP)

*** The only weird thing here is "Remote Server V5.1-14".  Since dbi won't
work with Rdb 5.1 could this have anything to do with it?  I don't know
where this information is coming from.  Possibly from dispatch as this
node has 5.1, 6.0 and 7.0 of dispatch installed.  But if so the same is
not true for node USDEV2.  That is node USDEV2 and dispatch 6.0 and 7.0
but remote server is 7.0.  I've posted note 333 in rdb_70 for more
clarification on where this info comes from and how we might be able
to change it.  It seems like the first 3 items (rdb, dispatch & server)
are on the remote node and the 2nd items (client, dispatch) are from
the dbi node.  But what is remote server?) ***

4.  If she creates a table to a nonexistent table in the udb on node USAOS
she gets the following error which is expected:

    metadata update failed import of object failed, 
    object does not exist in the target database.

So she is getting to the remote node and inside the remote rdb database.

5.  In the decdtm notes file I found one reference to these errors back
in 1991 and they were using an incompatible version of rdb and decdtm.
She is using the version of decdtm that comes with vms 6.2-1H3 and Rdb
is supported on that version.  Dbi is too right?  (6.1 or higher)
Checking that notes file found no patches for vms 6.2-1h3.

Thanks, Diane

One interesting thing came up.  She is using decnet 4 on one node and
decnet 5 on another.  Have a call in to her to find out which is on
which node (3 nodes involved).  Has dbi ever been tested with this?
There was a problem with rdb and vms 6.1 and below but she is on
vms 6.2-1h3.

Here is the trace:

EVENT: SDI_BRIEF (05/21/97 12:39:35) - Driver Dispatcher initialized
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Driver 6: Initialized
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Driver 6: Connection 33544776
established'
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Connection 33544776: Started
transaction
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Connection 33544776: Sub-request
33561760 compiled
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Connection 33544776: Sub-request
33561760 cursor opened
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Connection 33544776: Sub-request
33561760 cursor closed
EVENT: SDI_BRIEF (05/21/97 12:40:07) - Connection 33544776: Sub-request
33561760 released
EVENT: SDI_BRIEF (05/21/97 12:40:08) - Connection 33544776: Sub-request
33610856 compiled
EVENT: SDI_BRIEF (05/21/97 12:40:08) - Connection 33544776: Sub-request
33610856 cursor opened
EVENT: SDI_BRIEF (05/21/97 12:40:08) - Connection 33544776: Sub-request
33610856 fetched 0 tuples
EVENT: SDI_BRIEF (05/21/97 12:40:08) - Connection 33544776: Sub-request
33610856 cursor closed
EVENT: SDI_BRIEF (05/21/97 12:40:09) - Driver 1: Parsed link/proxy name
EVENT: SDI_BRIEF (05/21/97 12:40:09) - Driver 1: Initialized
EVENT: SDI_BRIEF (05/21/97 12:40:10) - Driver 1: Connection 33061720
established'
EVENT: SDI_BRIEF (05/21/97 12:40:11) - Connection 33061720: Started
transaction
EVENT: SDI_BRIEF (05/21/97 12:40:11) - Connection 33061720: Established
markpoint
---EVENT BEG: ERRORS --------------------------- Wed May 21 12:40:11.520
1997---
%RDB-E-DISTABORT, distributed transaction was aborted
-RDB-E-NOSECERR, cannot determine secondary error
---EVENT END: ERRORS --------------------------- Wed May 21 12:40:11.560
1997---

---EVENT BEG: ERRORS --------------------------- Wed May 21 12:40:11.570
1997---
%RDB-E-DISTABORT, distributed transaction was aborted
-RDB-E-NOSECERR, cannot determine secondary error
---EVENT END: ERRORS --------------------------- Wed May 21 12:40:11.600
1997---

---EVENT BEG: ERRORS --------------------------- Wed May 21 12:40:11.610
1997---
%RDB-F-IO_ERROR, input or output error
-SYSTEM-F-LINKABORT, network partner aborted logical link
---EVENT END: ERRORS --------------------------- Wed May 21 12:40:11.760
1997---

EVENT: SDI_BRIEF (05/21/97 12:40:11) - Connection 33061720: Retrieved table
metadata
---EVENT BEG: ERRORS --------------------------- Wed May 21 12:40:11.790
1997---
%DBI-F-IMPORT_FAIL, Import of object ROUTING_EQUIP_REL failed.
---EVENT END: ERRORS --------------------------- Wed May 21 12:40:11.810
1997---

---EVENT BEG: ERRORS --------------------------- Wed May 21 12:40:11.820
1997---
%RDB-E-NO_META_UPDATE, metadata update failed
---EVENT END: ERRORS --------------------------- Wed May 21 12:40:11.840
1997---

---EVENT BEG: ERRORS --------------------------- Wed May 21 12:40:11.860
1997---
%RDB-E-DISTABORT, distributed transaction was aborted
-RDB-E-NOSECERR, cannot determine secondary error
---EVENT END: ERRORS --------------------------- Wed May 21 12:40:11.880
1997---

EVENT: SDI_BRIEF (05/21/97 12:40:11) - Connection 33061720: Rolled back
markpoint
EVENT: SDI_BRIEF (05/21/97 12:40:15) - Connection 33061720: Rolled back
transaction
EVENT: SDI_BRIEF (05/21/97 12:40:15) - Connection 33544776: Rolled back
transaction

Hi,

This is fixed now.  Customer had rdbserver logical pointing to rdbserver.exe
5.1 on remote node.  Once they set that to point to 6.0 dbi was able to
link to a remote rdb db on that node.

Thanks, Diane