Conference orarep::nomahs::dbintegrator_public_public

    Forgot to mention in the previous note that this all works fine using
    SQLPLUS.
    
    Thanks,
    Don

Could this be the problem?   Note the line that says "The DBIG/Oracle 
incorrectly assumes that an index on a table is always owned by the owner 
of the table."  It says engineering was working on a fix but it looks
possible that one was never developed.

Note, there is a workaround but it may not be something the customer
wants to do.  

Thanks, Diane
--------------------------------------------------------------------------
[GTWYORA] LDRV-E-UNKNOWN_TABLE Error Occurs When Attaching to Oracle Database


Copyright (c) Digital Equipment Corporation 1995.  All rights reserved.

PRODUCT:    DEC DB Integrator Gateway for Oracle v3.*

OP/SYS:     OpenVMS VAX, OpenVMS AXP
            DEC OSF/1 AXP

SOURCE:     Digital Equipment Corporation


PROBLEM:

Attaching to an Oracle database through DEC DB Integrator Gateway for
Oracle (DBIG/Oracle) results in the following error:

ATTACH 'FILE /TYPE=ORACLE/USER=SCOTT/PASS=TIGER/NODE=T:MRDBSERV:MRDBSERV';

%SQL-F-ERRATTDEC, Error attaching to database
/TYPE=ORACLE/USER=SCOTT/PASS=TIGER
/NODE=T:MRDBSERV:MRDBSERV
-RDB-E-BAD_DB_FORMAT,
/DBKEY_DEFAULT_MODE=NATIVE/MAX_LONG_SIZE=512/NODE=T:MRDBSE
RV:MRDBSERV/NOENFORCE_ALL_TXN/PASSWORD=/TX_MODE=WARN_1PC/TYPE=ORACLE/USER=SCOTT
does not reference a database known to DEC DBI Gateway
-LDRV-E-BAD_META_QUERY, An error occurred executing a metadata query:
Table/Index Procedure
-RDB-E-BAD_DB_FORMAT,
/DBKEY_DEFAULT_MODE=NATIVE/MAX_LONG_SIZE=512/NODE=T:MRDBSE
RV:MRDBSERV/NOENFORCE_ALL_TXN/PASSWORD=/TX_MODE=WARN_1PC/TYPE=ORACLE/USER=SCOTT
does not reference a database known to DEC DBI Gateway
-LDRV-E-UNKNOWN_TABLE, Table O_SHI.KANAUFT not defined
                             ^^^^^^^^^^^^^

The attach works fine with /TABLE:

ATTACH 'FILE/TYPE=ORACLE/USER=SCOTT/PASS=TIGER
        /NODE=T:MRDBSERV:MRDBSERV/TABLE=KANAUFT';
                                        ^^^^^^^


ANALYSIS:

Table KANUAFT is owned by schema MR and not by schema O_SHI.  However,
there is an index defined on table KANAUFT and owned by schema O_SHI
and not schema MR.  Oracle allows indexes to be created on tables and owned
by different owners from the table owners.  The DBIG/Oracle incorrectly
assumes that an index on a table is always owned by the owner of the table.

To see if the above scenario is true, obtain the Oracle metadata by
executing the following queries in SQL*Plus.

    SQL> select aic.index_owner, aic.index_name, aic.table_name,
    ai.table_owner, aic.column_name
      2  from all_ind_columns aic, all_indexes ai
      3  where (aic.index_owner = ai.owner) and (aic.index_name =
    ai.index_name)
      4  and (aic.table_owner = ai.table_owner) and (aic.table_name =
    ai.table_name);

    SQL> select owner, table_name from all_tables;

    SQL> describe KANAUFT;


SOLUTION:

Engineering is working on a fix to be released in a future MUP kit.


WORKAROUND:

The workaround would be to drop the index currently owned by O_SHI on
this table and re-create the index with its owner being MR.

    Customer knows about the workaround, but wants the problem fixed. 
    
    Thanks,
    Don

    Seeing that this problem first occurred while DBI was owned by DEC
    should I create an official bug?  Or is this in the QAR system and
    that's good enough?
    
    Thanks,
    Don

    Bug # 476094