Question

我正在尝试根据Oracle的教程使用BISAMPLE创建存储库。 http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi1221/rpd/rpd.html http://rakeshpatil002.blogspot.com/2014/11/bisample-schema.html

Oracle数据库也是12c

用户已加载到ORCLPDB中。我将其加载到ORCL：之前，但在犯了该错误之后就删除了用户。

但是当我尝试添加它们时，出现以下错误消息。希望您能告诉我我做错了什么或应该去哪里解决这个问题。当我以BISAMPLE身份登录SQL Developer时，可以看到所有表。我的环境是Windows 2016 Server。

感谢您的帮助。（粗体字是错误）该错误来自管理工具。

元数据脚本执行错误：

inQSError: 28004 duplicate defininition
DECLARE TABLE "biplatform_datasource"."".""."SAMP_CUSTOMERS_D" AS "SAMP_CUSTOMERS_D"
 HAVING( 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."CUST_KEY" AS "CUST_KEY" TYPE DOUBLE PRECISION 53 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."NAME" AS "NAME" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."TYPE_KEY" AS "TYPE_KEY" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."FST_CONTACT_DT" AS "FST_CONTACT_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."SEGMENT_KEY" AS "SEGMENT_KEY" TYPE DOUBLE PRECISION 53 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."INCOME_LVL" AS "INCOME_LVL" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."STATUS_KEY" AS "STATUS_KEY" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."LST_ORDER_DT" AS "LST_ORDER_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."ADDRESS_KEY" AS "ADDRESS_KEY" TYPE DOUBLE PRECISION 53 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."MARITAL_ST" AS "MARITAL_ST" TYPE VARCHAR PRECISION 20 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."PREV_MARITAL_ST" AS "PREV_MARITAL_ST" TYPE VARCHAR PRECISION 20 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."PREV_MARITAL_ST_DT" AS "PREV_MARITAL_ST_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."BIRTH_DT" AS "BIRTH_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."CRDT_RATE" AS "CRDT_RATE" TYPE DOUBLE PRECISION 38 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    ERROR HERE
    **"biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."CUST_KEY" AS "CUST_KEY" TYPE DOUBLE PRECISION 53 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} ,**
    ERROR END
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."NAME" AS "NAME" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."TYPE_KEY" AS "TYPE_KEY" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."FST_CONTACT_DT" AS "FST_CONTACT_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."SEGMENT_KEY" AS "SEGMENT_KEY" TYPE DOUBLE PRECISION 53 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."INCOME_LVL" AS "INCOME_LVL" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."STATUS_KEY" AS "STATUS_KEY" TYPE VARCHAR PRECISION 1020 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."LST_ORDER_DT" AS "LST_ORDER_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."ADDRESS_KEY" AS "ADDRESS_KEY" TYPE DOUBLE PRECISION 53 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."MARITAL_ST" AS "MARITAL_ST" TYPE VARCHAR PRECISION 20 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."PREV_MARITAL_ST" AS "PREV_MARITAL_ST" TYPE VARCHAR PRECISION 20 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."PREV_MARITAL_ST_DT" AS "PREV_MARITAL_ST_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."BIRTH_DT" AS "BIRTH_DT" TYPE TIMESTAMP PRECISION 19 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} , 
    "biplatform_datasource"."".""."SAMP_CUSTOMERS_D"."CRDT_RATE" AS "CRDT_RATE" TYPE DOUBLE PRECISION 38 SCALE 0 NULLABLE VALUE TYPE  MAPPED COLUMN ''  MVLINK ''  DESCRIPTION  {} 
 );

Answer 1

史蒂夫

我们遇到了同样的错误。

我们用SELECT * FROM all_tables WHERE TABLE_NAME = 'SAMP_ADRESSES_D'检查了Oracle数据库的元数据目录中的条目数：

发生了两次。

我们发现有两个不同的所有者：BISAMPLE和BISAMPLE_EXA。

我们丢下桌子了

DROP TABLE BISAMPLE_EXA.SAMP_ADDRESSES_D

发现在新存储库的配置对话框中，SAMP_ADRESSES_D的重复条目消失了。

我们对Oracle BI培训指南中提到的所有重复表重复了DROP TABLE步骤（我想您使用的是相同的步骤）。

我们观察到所有重复项均已删除，并且向导允许我们继续。

此后，我们的机器遭受了虚拟的心脏病发作，并发出蓝色的死亡提示：-（

尽管如此，我们还是解决了您可能也遇到的问题。显然，这是Oracle BI中的错误。他们无法区分具有相同对象名称的不同所有者的对象。如果您知道为Oracle开发人员（例如Microsoft Connect）的开发人员描述此错误的位置，请随时将其添加到该错误中。

最诚挚的问候

JP

OBIEE 12c管理工具-重复定义-元数据脚本执行错误

1 个答案: