0

我正在尝试按照 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: 之前，但在犯了那个错误后删除了用户。

但是当我尝试添加它们时，我收到以下错误消息。我希望你能告诉我我做错了什么或者我应该在哪里解决这个问题。当我在 SQL Developer 中以 BISAMPLE 身份登录时，我可以看到所有表。我的环境是 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  {} 
 );
4

1 回答 1

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消失了。

DROP TABLE正如我们的 Oracle BI 培训指南中提到的那样，我们对所有重复的表重复了该步骤（我猜你使用的是相同的）。

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

在那之后，我们的机器遭受了一次虚拟的心脏病发作，由蓝色的死亡碎石表示:-(

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

此致

J.P

于 2019-07-12T19:22:19.313 回答