MDL Import in OWB 10gr2

I am getting this error, while doing import of MDL file. Anybody has had this error.
Query : insert into pctree values(?, ?, ?, ?) isUpdatable : false isBatch : trueSQL Error : ORA-00001: unique constraint (REPOWNR2.IDX_PCTREE_CHILDID) violated
Query : insert into pctree values(?, ?, ?, ?) isUpdatable : false isBatch : trueSQL Error : ORA-00001: unique constraint (REPOWNR2.IDX_PCTREE_CHILDID) violated
Repository Error:SQL Exception..
Class Name: MCMService.
Method Name: executeQuery.
Repository Error Message: java.sql.SQLException: ORA-00001: unique constraint (REPOWNR2.IDX_PCTREE_CHILDID) violated
     at oracle.wh.repos.pdl.mcm.MCMUtils.executeQuery(MCMUtils.java:163)
     at oracle.wh.repos.pdl.mcm.MCMUtils.executeQuery(MCMUtils.java:95)
     at oracle.wh.repos.pdl.mcm.MCMAssociations.syncAssociationTables(MCMAssociations.java:64)
     at oracle.wh.repos.pdl.mcm.MCMServiceImpl.afterPersist(MCMServiceImpl.java:3089)
     at oracle.wh.repos.pdl.foundation.DirtyCache.persist(DirtyCache.java:310)
.............

Hi
I'm facing the same issue, this is the error I got after trying to import a map from MDL via control file. I haven't found any solutions in here, would appreciate a piece of advice.
Detailed Error Message:
Query : insert into pctree values(?, ?, ?, ?) isUpdatable : false isBatch : trueSQL Error : ORA-000
01: unique constraint (OW
BREPO.IDX_PCTREE_CHILDID) violated
Trying to import a map from MDL via control file using the OMB command below:-
OMBIMPORT MDL_FILE 'UPGRADE.mdl' USE REPLACE_MODE MATCH_BY NAMES CONTROL_FILE 'control_file.txt' OUTPUT LOG 'control_file.log'
control file looks like this:-
MODE=ACTIONPLAN
ACTION=REPLACE
PROJECT=P_TEST
ORACLE_MODULES=M_REST
MAPPINGS=MAP_TEST
##

Similar Messages

  • Issues with MDL imports in OWB

    I am trying to import MDL files, some MDL's import was success when i started importing MAPPING MDL's i am getting below error, i am completly new to this OWB world,can some one help me on this issue.
    * Oracle Warehouse Builder Import Log File
    * Created: Dec 17, 2011 7:47:05 PM
    * OWB Release: 11.1.0.7.0 OWB Repository Version: 11.1.0.7.0 MDL Release: 10.2
    * User: null Connect String: null
    * Data File: /u01/oracle/MOC/db/tech_st/11.1.0/owb/rtp/sql/mdl/r12rfrmp.mdl
    * Log File: /u01/oracle/MOC/db/tech_st/11.1.0/owb/rtp/sql/mdl/r12rfrmp_imp.log Log Message Level: ALL
    * Character Set: UTF8
    * Mode: UPDATE Ignore Universal Identifier: Y
    Import started at Dec 17, 2011 7:47:05 PM
    Importing into workspace OWBADMIN
    Informational: MDL1328: PROJECT MTH not imported since the object in MDL file is the same as the object in the workspace.
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR> not found for OPERATOR <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.MTH_ENTITY_PLANNED_USAGE_ERR>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR> not found for GROUP <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.INOUTGRP1>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ENTITY_FK> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ENTITY_FK>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ENTITY_TYPE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ENTITY_TYPE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_AUDIT_DETAIL_ID> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_AUDIT_DETAIL_ID>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_AUDIT_RUN_ID> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_AUDIT_RUN_ID>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_ERROR_ID> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_ERROR_ID>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_ERROR_OBJECT_NAME> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_ERROR_OBJECT_NAME>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_ERROR_REASON> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_ERROR_REASON>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_OPERATOR_NAME> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_OPERATOR_NAME>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_SEVERITY> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_SEVERITY>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR_CODE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR_CODE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.PERIOD_OF_USAGE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.PERIOD_OF_USAGE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.PLANNED_USAGE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.PLANNED_USAGE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.REPROCESS_READY_YN> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.REPROCESS_READY_YN>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.SUSTAIN_ASPECT_FK> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.SUSTAIN_ASPECT_FK>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR> not found for OPERATOR <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.MTH_ENTITY_PLANNED_USAGE_ERR_1>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR> not found for GROUP <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.INOUTGRP1>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ENTITY_FK> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ENTITY_FK>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ENTITY_TYPE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ENTITY_TYPE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_AUDIT_DETAIL_ID> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_AUDIT_DETAIL_ID>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_AUDIT_RUN_ID> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_AUDIT_RUN_ID>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_ERROR_ID> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_ERROR_ID>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_ERROR_OBJECT_NAME> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_ERROR_OBJECT_NAME>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_ERROR_REASON> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_ERROR_REASON>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_OPERATOR_NAME> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_OPERATOR_NAME>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR$$$_SEVERITY> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR$$$_SEVERITY>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.ERR_CODE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.ERR_CODE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.PERIOD_OF_USAGE> not found for ATTRIBUTE <MTH.MTH_TARGET.MTH_ENT_PLANNED_USG_ES_ALL_MAP.PERIOD_OF_USAGE>
    Warning: MDL3002: ReferencingObject <MTH.MTH_TARGET.MTH_ENTITY_PLANNED_USAGE_ERR.PLANNED_USAGE> not found for ATTRIBUTE

    It sounds like the MDL has mappings and the dependent tables referenced by the mappings are not in that MDL...they may be in another one, you should import it first. If not, then export from a repository which has the tables.
    Cheers
    David

  • Deployment hangs after importing metadata OWB 10gR2

    Hi folks,
    in development I created a new mapping with I exported/imported into test enviroment.
    I did this using "import all objects, update metadata, match by UID".
    When I try to deploy the imported mapping ControlCenter hangs showing the green arrow.
    In the DOS box where I started the client it says:
    </OBJECT>
    </OBJECT>
    </OBJECT>
    </NAMESPACE>
    RUNTIME_SERVICES_DEBUG [WhValidationGenerationTransaction] DeploymentUtils.isAda
    pterFCO(WBGeneratedObject): Not found objectTypeName CMPMap defaulting to FCO
    RUNTIME_SERVICES_DEBUG [WhValidationGenerationTransaction] DeploymentSpecificati
    onImpl.addToUnitSpecificationImplArrayList: created UnitSpecification for Deploy
    mentAdapterName DDLDeployment StoreUOID= 9B7415EC7AB94F54824DF5F57D502828 Action
    = 1 FCO list= M_FUNDSTRUCT_DWH,
    Runtime Parameters for : M_FUNDSTRUCT_DWH
    SYSTEM: DEFAULT_OPERATING_MODE: SET_BASED_FAIL_OVER_TO_ROW_BASED
    SYSTEM: DEFAULT_AUDIT_LEVEL: ERROR_DETAILS
    SYSTEM: MAXIMUM_NUMBER_OF_ERRORS: 50
    SYSTEM: COMMIT_FREQUENCY: 1000
    SYSTEM: BULK_SIZE: 1000
    SYSTEM: DEFAULT_PURGE_GROUP: WB
    SYSTEM: ANALYZE_TABLE_SAMPLE_PERCENTAGE: 5
    RUNTIME_SERVICES_DEBUG [WhValidationGenerationTransaction] ExecutionUtils.decode
    SystemParameter: Unexpected parameter ANALYZE_TABLE_SAMPLE_PERCENTAGE
    Notification (Unit): start VEVA_LOCATION (Erstellen) - 0 (Adapter=DDLDeployment
    Location=VEVA_LOCATION)
    MEM:GenerationValidationService:internalCompile:after transaction:U: 65237816%IN
    CR:2538296:INCREASE
    What is the problem?
    Michael

    The error is due to the corrupted MDL file. MDL is getting corrupted because there is not enough memory for java VM. To fix the MDL corruption increase memory parameters.
    1. On client PC: XXXX\owb\bin\win32\owbclient.bat change
    java -Xms64M -Xmx768M -Dlimit=768M -XX:MaxPermSize=256M
    to
    java -Xms64M -Xmx1024M -Dlimit=1024M -XX:MaxPermSize=512M
    Restart client session.
    It did fix the problem in my case.
    Oracle also recommends changing memory parameters on the server side (UNIX in my case)
    2.On server side XXXX/owb/bin/unix/run_service.sh
    $JAVAPATH/bin/java -Xmx768M
    to
    $JAVAPATH/bin/java -Xmx1024M

  • MDL files not readable in OWB 10gR2?

    I have exported an MDL file in OWB 10gR2 for an entire OWB Project (using Design -> Export -> Warehouse Builder Metadata in the Design Center). I noticed that the resulting MDL file is not in readable ASCII format (unlike previous releases such as OWB 9i).
    Is this the expected behaviour?
    I guess it doesn't really matter what format it is in, since I was able to delete a table from the repository using the Design Center GUI and then re-create it in the repository by importing my MDL file.

    Alas, it seems that the export is now a binary file. This probably has some real benefits somewhere, but I for one am not keen on it. There have been scenarios where I had to alter the MDL file manually to re-import it, but should such an occation present itself again, I won't be able to.
    Not that I have been able to migrate to 10gR2 yet, due to a bug, that I might be able to fix myself if I had access to plaintext MDL file ...
    Borkur

  • OWB 10gr2 - MDL1601 and MDL1201 - Metadata Import Problems

    I am running OWB 10gr2 on top of a 10gr2 database for the repository. I'm trying to do an export of an entire project into MDL, and then import it into another repository in a different environment, with same setup (both OWB and database are 10gr2 there as well).
    The export goes fine, but when trying to import, I get two different error messages:
    1) After selecting the MDL file to import, if I click the "Import" button I get a-
    "MDL1601: Cannot import because the base language in the MDL file is missing"
    2) Also if I try to click the "Show Summary" or "Advanced..." buttons on the import screen, I instead get a-
    "MDL1201: Import file is not valid. Metadata Loader release must by specified in import data file using the MDLRELEASE keyword."
    As to the first error, I have verified in my source repository that the Base Language is in fact listed as "American English", and have even gone so far as to add basic "English" as an additional display language using the repository assistance, but this brings no improvement.
    As to the second error, I have already found the post here in the forums explaining that it is due to a corrupted MDL file because of insufficient Java VM memory. However, I have tried the solution recommended there, also with no improvement. (it is here: Re: MDL1201: Import data file is not valid.
    Any help that someone can provide would be greatly appreciated. For purposes of backing up my repository project, I'm getting concerned that if I ever needed to, I'd never be able to restore from a MDL export file!
    Thanks in advance for any help.

    The error is due to the corrupted MDL file. MDL is getting corrupted because there is not enough memory for java VM. To fix the MDL corruption increase memory parameters.
    1. On client PC: XXXX\owb\bin\win32\owbclient.bat change
    java -Xms64M -Xmx768M -Dlimit=768M -XX:MaxPermSize=256M
    to
    java -Xms64M -Xmx1024M -Dlimit=1024M -XX:MaxPermSize=512M
    Restart client session.
    It did fix the problem in my case.
    Oracle also recommends changing memory parameters on the server side (UNIX in my case)
    2.On server side XXXX/owb/bin/unix/run_service.sh
    $JAVAPATH/bin/java -Xmx768M
    to
    $JAVAPATH/bin/java -Xmx1024M

  • Can an MDL export from OWB 9.0.3.37 be imported into OWB10g?

    Folks, instead of upgrading our existing development repository, we are planning to install a brand new OWB. Can we import the MDL export from OWB 9.0.3.37 into OWB 10gR1? Are there any gotchas? Any help is appreciated.

    I`ve tried these steps, but can`t because of the following error message:
    CNV00002-0038(ERROR): El idioma de origen English con identificador ISO en no están en la lista de idiomas soportados.
    Any suggestion?.
    Thanks.
    Leonardo.

  • OWB 10gR2 on DB 11g and Workflow installation

    Hi all,
    my customer has a data warehouse running on Oracle DB 10gR2 - 2 nodes RAC - on Linux 32 bit (Red Hat enterprise 5);
    ETL is developed with OWB 10gR2 and exploits Oracle Workflow (2.6.4).
    They are going to upgrade the database to 11.1 (still 2 nodes RAC) on Linux 64 bit (Red Hat enterprise 5),
    and they would prefer to avoid OWB upgrade.
    On Oracle Support, it seems that OWB 10gR2 is certified on DB 11.1,
    so our idea is to install a OWB 10gR2 repository on DB 11.1 and then export/import MDL
    from current repository (OWB 10gR2 on DB 10gR2) to the new repository (OWB 10gR2 on DB 11.1).
    My first question is related to Workflow:
    is it correct to install Workflow on the new DB 11.1 using the software available in the home of OWB 11g software ?
    is it guaranteed thet OWB 10gR2 installed on DB 11.1 will have no problems in using such installation of OWF ?
    or should we install OWF 2.6.4 on DB 11.1 using the same software that was installed on db 10gR2 ?
    My second question is related to *32 bit vs 64 bit platform*;
    intuitively, we should install the 64 bit version of OWB 10gR2 (and OWF) on the new plaftorm hosting DB 11g:
    is ita potential issue for the OWB repository migration ?
    on our pc of course we will go on using OWB Client 32 bit: are there compatibility problems?
    Thanks
    Silvio

    Hi Silvio,
    is it correct to install Workflow on the new DB 11.1 using the software available in the home of OWB 11g software ?It is better to use Oracle Workflow from DB 11g.
    is it guaranteed thet OWB 10gR2 installed on DB 11.1 will have no problems in using such installation of OWF ?As I know DB 11gR1 contains also 2.6.4 Workflow release, so you won't have any problem
    My second question is related to 32 bit vs 64 bit platform;
    intuitively, we should install the 64 bit version of OWB 10gR2 (and OWF) on the new plaftorm hosting DB 11g:
    is ita potential issue for the OWB repository migration ?IMHO it is not problem
    on our pc of course we will go on using OWB Client 32 bit: are there compatibility problems?There are no any problem with 32bit OWB client and OWB repository on 64bit platform
    Regards,
    Oleg

  • OWB 9.0.4 metadata import from OWB 9.0.3.33

    We have created an export file of the metadata from version 9.0.3.33 and upgraded it with the mdl upgrade utility.
    When we tried to import this file into version 9.0.4 the following error occurred:
    Import for OWB Release: 9.0.4.8.21 Version: 9.0.4.0.27
    * Physical Names: Y Mode: CREATE Character Set: WE8MSWIN1252
    * Ignore Universal Identifier: N Commit At End: Y
    Informational at line 29: MDL1205: PROJECT with Unique Object ID (UOID) &lt;9E011EFAD16211D48D7100B0D02A59E8&gt; already exists, so PROJECT with physical name &lt;MY_PROJECT&gt; and business name &lt;My Project&gt; not imported.
    Error at line 30,625: MDL1247: Error occurred importing mapping &lt;CONT_MAPPING/CONT_MAPPING&gt; (at line 30,624).
    Detailed Error Message:
    MDL1259: Error reconciling MAPPINGSTAGECOMPONENT &lt;contract_dat/contract_dat&gt; for MAPPING CONT_MAPPING/CONT_MAPPING.
    java.lang.ArrayIndexOutOfBoundsException
         at oracle.wh.service.impl.mapping.metadata.WBReconcileServiceImpl.internalReconcileProperty(WBReconcileServiceImpl.java:1397)
         at oracle.wh.service.impl.mapping.metadata.WBReconcileServiceImpl.internalReconcilePropertyOwner(WBReconcileServiceImpl.java:1199)
         at oracle.wh.service.impl.mapping.metadata.WBReconcileServiceImpl.reconcileComponent(WBReconcileServiceImpl.java:853)
         at oracle.wh.service.impl.mapping.metadata.WBReconcileServiceImpl.internalExecuteReconcilePlan(WBReconcileServiceImpl.java:475)
         at oracle.wh.service.impl.mapping.metadata.WBReconcileServiceImpl.executeReconcilePlan(WBReconcileServiceImpl.java:373)
         at oracle.wh.service.impl.metadataloader.WBImportMapping.reconcileStageComponentByPlan(WBImportMapping.java:3404)
         at oracle.wh.service.impl.metadataloader.WBImportMapping.reconcileStageComponents(WBImportMapping.java:3222)
         at oracle.wh.service.impl.metadataloader.WBImportMapping.processKeyword(WBImportMapping.java:4282)
         at oracle.wh.service.impl.metadataloader.WBImportMapping.importMapping(WBImportMapping.java:4548)
         at oracle.wh.service.impl.metadataloader.WBImport.process(WBImport.java:5653)
         at oracle.wh.ui.metadataloader.WBMetaDataImportTransaction.run(WBMetaDataImportTransaction.java:105)
    PLEASE HELP!!!

    Thank you for you postings - The Member Feedback forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. However we recommend that you post this thread to the "Oracle Warehouse Builder" forum.
    The URL is: Warehouse Builder
    Thanks - The OTN team

  • OWB 10gR2: Why is CWM Export desupported?

    Hi,
    Does anyone know why it is in OWB 10gR2 no longer possible to do CWM exports (OMG CWM format)?
    Regards
    Maurice

    So how do I create an CWM .xml file to import metadata into e.g. Cognos starting from 10gR2 without purchasing a third-party tool (MIMB)?
    I've seen numerous vague answers, can someone please clarify this finally: can it be done and if yes, how?
    regards,
    Jurgen

  • MDL IMPORT FAILS WITH MDL1261

    Hi all,
    I am using the OWB Repository Version 10.2.0.4.0 in a AIX server and we face MDL IMPORT FAILS WITH MDL1261
    On Oracle Metalink we found the following information. The datatype and background both are set to 113.
    Does the suggestion to set the values to 10007 apply in this case?
    Thanks !
    Sebastian
    MDL IMPORT FAILS WITH MDL1261
    The upgrade to 11.1.0.7 creates a new property SAP_FTP in the repository. The DATATYPE of this property is incorrectly set to113. The value should be 10007. This wrong datatype causes the NullPointerException because it causes the type not be found when it is expected to be there.
    Solution
    1. Using SQL*Plus, connect to OWBSYS
    2. Check datatype of property SAP_FTP
    SQL> select name, datatype from PROPERTYDEFINITION_V where name = 'SAP_FTP';
    NAME DATATYPE
    SAP_FTP 113
    3. Check datatype of property BACKGROUND
    SQL> select name, datatype from PROPERTYDEFINITION_V where name = 'BACKGROUND';
    NAME DATATYPE
    BACKGROUND 10007
    The value of DATATYPE for the property SAP_FTP and property BACKGROUND should be the same (10007). If this is not the case, the DATATYPE of property BACKGROUND should be changed.
    Proceed to the next step to correct this.
    4. Update PROPERTYDEFINITION_V
    If the value of DATATYPE is not the same for property SAP_FTP and property BACKGROUND, then correct this as follows:
    SQL> update PROPERTYDEFINITION_V
    set DATATYPE = (select datatype from PROPERTYDEFINITION_V where name = 'BACKGROUND') where name = 'SAP_FTP';
    5. Verify updated correctly
    SQL> select name, datatype from PROPERTYDEFINITION_V where name = 'SAP_FTP';
    NAME DATATYPE
    SAP_FTP 10007
    6. If everything looks correct, then commit.
    SQL> commit;
    Commit complete.

    Hi Detlef,
    This is the only error I got. Regards, Sebastian
    error at line 237,069: MDL1261: Error importing MAPPING GG_OPS.4_DWH.GG_MAP_D_OFFICE.
    Detailed Error Message:
    java.lang.NullPointerException
         at oracle.wh.repos.impl.foundation.CMPElement.setElement(CMPElement.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.WBProxy.uncached(WBProxy.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.StaticCache.uncache(StaticCache.java:120)
         at oracle.wh.repos.pdl.foundation.CacheMediator.uncacheComponent(CacheMediator.java:1435)
         at oracle.wh.repos.pdl.foundation.UncacheService.uncache(UncacheService.java:495)
         at oracle.wh.repos.pdl.foundation.UncacheService.uncache(UncacheService.java:346)
         at oracle.wh.repos.pdl.foundation.UncacheService.uncache(UncacheService.java:640)
         at oracle.wh.repos.pdl.foundation.MemoryManagerImpl.uncache(MemoryManagerImpl.java:530)
         at oracle.wh.repos.pdl.foundation.MemoryManagerImpl.checkMemory(MemoryManagerImpl.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.CacheMediator.cache(CacheMediator.java(Compiled Code))
         at oracle.wh.repos.pdl.foundation.CacheMediator.cache(CacheMediator.java(Compiled Code))
         at oracle.wh.repos.impl.ProxyFactoryGen.createCMPMap(ProxyFactoryGen.java:4482)
         at oracle.wh.repos.impl.ProxyFactoryGen.createCMPMap(ProxyFactoryGen.java:4468)
         at oracle.wh.repos.impl.ProxyFactoryGen.createCMPMap(ProxyFactoryGen.java:4463)
         at oracle.wh.repos.pdl.metadataloader.MDLImportCreateUtil.internalImportObject(MDLImportCreateUtil.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.MDLImportCreateUtil.importObject(MDLImportCreateUtil.java(Inlined Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElementCreateObj(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElement(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.processPendingFCOElements(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElementPendingFCOAssoc(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.startElement(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.Import.OutputMDLImport.run(OutputMDLImport.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ConverterStateMachine.runAll(ConverterStateMachine.java(Compiled Code))
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ProcessXML$ConvertHandlerBase.startElement(ProcessXML.java(Compiled Code))
         at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java(Compiled Code))
         at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:326)
         at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:293)
         at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:295)
         at oracle.wh.repos.pdl.metadataloader.converter.util.WBXMLSourceReader.parse(WBXMLSourceReader.java:59)
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ProcessXML.runConversion(ProcessXML.java:356)
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.ProcessXML.run(ProcessXML.java:290)
         at oracle.wh.repos.pdl.metadataloader.converter.foundation.StateMachine.runAll(StateMachine.java:50)
         at oracle.wh.repos.pdl.metadataloader.converter.WBConverter.ConvertXML(WBConverter.java:568)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLImport.process(MDLImport.java:1859)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.internalRunImport(MDLRunImport.java:431)
         at oracle.wh.repos.pdl.metadataloader.Import.MDLRunImport.runImport(MDLRunImport.java:503)
         at oracle.owb.Import.ImportServiceManager.internalImportMetaData(ImportServiceManager.java:506)
         at oracle.owb.Import.ImportServiceManager.importMetaDataFromFile(ImportServiceManager.java:355)
         at oracle.owb.scripting.executers.ImportCmdExecuter.startMetaDataImportCommand(ImportCmdExecuter.java:708)
         at oracle.owb.scripting.executers.ImportCmdExecuter.importFromFile(ImportCmdExecuter.java:150)
         at oracle.owb.scripting.parsers.ImportCmdParser.mdlImportCommand(ImportCmdParser.java:302)
         at oracle.owb.scripting.parsers.ImportCmdParser.ImportCommand(ImportCmdParser.java:152)
         at oracle.owb.scripting.parsers.ImportCmdParser.parseCommand(ImportCmdParser.java:112)
         at oracle.owb.scripting.commands.OMBMetaDataImportCmd.executeCommand(OMBMetaDataImportCmd.java:77)
         at oracle.owb.scripting.commands.OMBCommand.cmdProc(OMBCommand.java:69)
         at tcl.lang.Parser.evalObjv(Parser.java:818)
         at tcl.lang.Parser.eval2(Parser.java:1221)
         at tcl.lang.Interp.eval(Interp.java:2189)
         at tcl.lang.Interp.evalFile(Interp.java:2368)
         at tcl.lang.TclShell.run(TclShell.java:124)
         at tcl.lang.TclShell.run(TclShell.java:68)
         at oracle.owb.scripting.OMBShell.main(OMBShell.java:38)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
         at java.lang.reflect.Method.invoke(Method.java:391)
         at Launcher.main(Launcher.java:167)

  • MDL Import Problem

    Hi,
    While importing .mdl, I am getting the following error:
    Import started at 09/12/2005 9:44:10 AM
    * Import for OWB Release: 10.1.0.3.0 Version: 10.1.0.3.0
    * User: hussain10g Connect String: (DESCRIPTION=(ADDRESS=(HOST=147.149.178.210)(PROTOCOL=tcp)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=uiid.devenv1.bt.co.uk)))
    * Definition File: null
    * Data File: C:\Documents and Settings\937664\Desktop\R2_29_MDL_BACKUP_OFF\SAJ_UII_R229_DEV-20050912_0919.mdl
    * Log File: C:\Documents and Settings\937664\Desktop\R2_29_MDL_BACKUP_OFF\Log.log Log Message Level: ALL
    * Physical Names: Y Mode: UPDATE Character Set: WE8MSWIN1252
    * Ignore Universal Identifier: Y Commit At End: Y
    Error at line 29,408: MDL1247: Error occurred importing mapping <UII_MAP_SPC_ALARM_SRCH_PERIOD/UII_MAP_SPC_ALARM_SRCH_PERIOD> (at line 29,408).
    Detailed Error Message:
    PRS-00305: Could not reserve the name due to an internal error. Please contact Oracle Support with the stack trace and details on how to reproduce it.
    Can any tell me what is the cause of this error.
    Regards,
    Liyakat

    Hello,
    are you importing with OWB client or OMBPlus?
    If you imported the metadata with the client try to import with OMBPlus:
    OMBCONNECT user/[email protected]:1521:DB USE SINGLE_USER_MODE
    OMBIMPORT FROM MDL_FILE 'xyz.mdl' OUTPUT LOG TO 'xyz.log'
    OMBCOMMIT
    OMBDISCONNECT
    Regards Franz

  • OWB 10gR2 - some enhancement requests

    Hi, I've been working with OWB 10gR2 for approximately a week now, and I've come across a few (minor) bugs, as well as a list of enhancements that I think would make the tool better. I'd like to surface these in this forum so they can be either disagreed with or have workarounds suggested, as well as getting this list in front of Oracle. Also I'm new to the tool, so maybe there are ways to accomplish what I want.
    p.s. as a side note - please don't take these as criticisms of the tool. I'm actually very impressed with OWB 10gR2, but just want to surface some ideas that I think would make the tool better.
    Thanks,
    Scott
    ---Bugs:
    1.     If I enter a quote character in one of the business description fields (i.e. for a cube or dimension), it causes the DDL scripts to blow up. It probably mentions the list of valid characters in the users guide somewhere - but if a character isn't legal, it should be flagged when I try to enter it originally – not when deploying
    2.     I can enter illegal strings in an expression operator that fail validation there, but the whole map still passes validation. For instance, I put in an expression (for a varchar2 field) using a single quote at the start, but mistakenly with a double quote at the end. I didn’t bother to validate this within the expression. The whole map validated fine, but (of course) blew up with the illegal syntax when generating the code.
    3.     I get the following error when trying to browse a cube (ROLAP, not MOLAP) through OWB, but I'm able to pull the cube up fine using either the excel add-in or biBeans: CubeDV_OLAPSchemaConnectionException_ENT_06952???
    ---Enhancement Requests:
    1.     Add a “deploy” button in control center next to the to “default actions” and “reset actions” buttons
    2.     Allow an option to have dimensions and cube defaults set to either “deploy all”, “deploy data only”, “deploy catalog only”, “deploy aggregations” (for cubes). Also, why is the default set to “deploy data only”? Does deploying the CMW2 metadata involve huge performance impacts or something? It seems like the CMW2 is almost “free” – so it should be turned on by default. Its a pain to use the dimension wizard, but then have to go in to each dimension afterwards to set this option.
    3.     When using “configure” on dims and cubes in control center, the first time the “configuration properties” dialog pops up, everything is fine. However, when you try to configure the 2nd object, the “background focus” switches from control center back to design center. This makes navigation very slow if you have lots of items to change. I've noticed this behavior in a few other places as well.
    4.     Some dialogs do not have maximize buttons (i.e. dimension wizard dialogs), and default to a very small size. It is possible to have size of dialogs dynamically scaled to screen resolutions, and attempt to size columns so they fit properly. Or better yet, have each dialog remember how large it was last time, and automatically open up to that size?
    5.     When generating the “autobind” relational table while creating a dimension, it seems to be “randomizing” the order of the attributes within a level (although it does sort the “top level” attributes first, followed by lower level attributes), at least when using the dimension wizard. It would be nice if the attributes in the relational table came out sorted in the same order as they are specified in the attributes tab.
    6.     When using a “unmapped” display set– there doesn’t seem to be a way to refresh the set (i.e. remove the items that have since been mapped) unless you select “all” and then “unmapped” again. Would be nice if you could simply choose “unmapped” again and have it refresh the object
    7.     While doing a mapping, right click on canvas allows option to “generate”. Would be nice to also add the “validate” option to this menu
    8.     Validating mappings takes a decent amount of time – would be nice if a “busy” icon was displayed to let user know that OWB hasn’t locked up.
    9.     default size of “job details” dialog is too small, and even if I maximize I still have to go through and manually adjust the size of each pane. Similar to enhancement #4
    10.     Horizontal size of operators in mapping seems to be determined by the length of the operator name, instead of tying directly to the icon. Looks strange. Very minor
    11.     When displaying dimension objects in a mapping:
    a.     For the “surrogate key” columns – add an icon to indicate this attribute is a surrogate key. Likewise, since its not legal to map anything to this column, remove the little “arrow” next to it (the one that turns gray when something is mapped to a column), or perhaps don't even show this column at all.
    b.     For the “business key” columns – add some type of icon to show which attributes represent the business natural key (or make color different, etc.)
    12.     Similar to #11, for the cube operator in a mapping:
    a.     For the “surrogate key” columns – if they can’t be mapped to, then don’t show them
    b.     For the “business key” columns – add some type of icon to show which attributes represent the business natural key
    c.     Separate the “measure” columns from the dimension columns
    13.     For the “Aggregation” operator – can you move the “<None>” default operator to the top of the list. At the bottom, it means you always have to scroll to use the most common operations (which are at the top of the list), i.e. sum and avg, etc.
    14.     In the log on prompt, if I choose SQL*Net connection, every time I start it up it defaults to the details being shown (even when I chose no detail last time), with cursor in the “host” box. I should be able to have the details hidden, and this dialog should ALWAYS default to having the active cursor in the password box on startup
    15.     When printing in a mapping, the “page setup” print dialog is very slow. Also, the “print setup” dialog shows margins, but you can’t adjust them. It would be nice if this could be changed here
    16.     Add a “print preview” icon to all of the toolbars. Printer icon is there, print preview should also be.
    17.     In the dimension attributes, we need a way to tag an attribute as being the “insert record” date or the “update record” date. The corresponding MERGE SQL should be updated to use these attributes.
    18.     It would be nice if the mapping canvas defaulted to an unlimited size…i.e. when I want to add new operators and the screen is already full, I either need to shrink the zoom factor down to the point where I can’t read the icons anymore, or I have to pick up the new operator and “drag” at the bottom / right side until it scrolls enough to drop it where I want. If the canvas had an unlimited size, I could simple use the scroll bars to scroll to where I want.
    19.     Scroll wheel functionality to zoom in / out (and have it zoom in around the currently selected object)
    20.     Option to have operations automatically resize when longer attribute names are added to them (can workaround by mimimizing and then maximizing, but would be better to have the operators automatically adjust size to fit)
    21.     Ability to sort output attributes in an operator (just like table column sort functionality). If I create a new operator, it would be nice to group it with related operators instead of always having it at bottom.
    22.     re: column sort functionality – drag and drop instead of up/down arrows would be nice
    23.     It would be nice if, when adding output attributes to (for example) the expression operator, it would choose the default data type the same way the dimension attribute wizard works (i.e. if it sees “ind” in name, automatically choose char(1)
    24.     Change the “zoom in” button so that it zooms in on the currently selected operator – i.e. if I click on a particular table and then hit the zoom in button, it should keep the table I selected centered
    25.     When in a mapping, clicking on a line should highlight the attributes on both the source and target operators (to allow easier visual ID of where data is coming from / going to)
    26.     AWM has a feature where table attributes can be sorted so that mappings between them don't have "crossed" lines. Similar functionality in OWB would be very appreciated. It may be harder to automate this, but even manual drag and drop of attributes within an operator would be nice.

    if you could copy/paste this whole thing into the submission form (see feedback option under the numbers menu). The more people that request these features, the more likely we are to see them in an update or the next version.
    Jason

  • Unable to use XML functions in OWB 10gR2.

    Hi,
    I am trying to use XMLELEMENT ,XMLATTRIBUTES and XMLFOREST function for loading into a XML file using OWB 10Gr2.
    During deployment it is erroring out with an error 'identifier 'XMLELEMENT' must be declared'.
    Please suggest some workaround or possible reason for this problem.
    Reagrds,
    PHD
    Edited by: user1662077 on May 21, 2009 5:17 AM

    Hi Navneet,
    I have followed these steps,But beyond that there is some thing which we want to achive.
    We want the xml file to have a proper format like
    "<?xml version="1.0" encoding="UTF-8"?>
    <Header recTyp ='01' RTA='IN200200' ISIN='IN2000020220' recDate ='20090202' stmtDate='20090202' stmtTime='232020'
    totNSDLPos='100' totTrnstPos='0' TotUnlckPos='10' TotLckPos='100' totPldgPos='0' totFrzPos='9' totIdtPos='9'
    NSDLTotFrzPos='1' totDtlRec='2'/>
    <Details recTyp='02' dpId='IN300118'>
    <BenDtl benAcctNum='12345678' type='01' subtype='02' status='01'>
    <FirstHldr name='op' fatherName='' PAN='HUFSOSFNKS'>
    <Address type='1' pinCode='400097' phoneNum='28490520' faxNum='9999999999'>
    <Part type='1'>
    </Part>
    <Part type='2'>
    </Part>
    <Part type='3'>
    </Part>
    <Part type='4'>
    </Part>
    </Address>
    </FirstHldr>.........."
    On the oracle blogs it was suggested that this can be achived by using XML function in the expression operator.
    But while using them,OWB is not recongnising these XML function.
    Regards,
    PHD

  • OWB 10gR2 : How to configure ctl and log locations for Sql*Loader mappings?

    Hi all,
    I'm using OWB 10gR2 to load data in tables with Sql*Loader mappings.
    In my project I have a datafile module and an Oracle module.
    When creating an sql*loader mapping in the oracle module, there is two properties for this mappings that I want to modify. The first is Control File Location and the second is Log File Location. Values for those properties are equal to the data file module location. When trying to change those values I can only chose "Use module configuration location".
    Somebody knows how to configure those properties with different locations as the one of the flat file module?
    What I want to do is to store the data file in one directory, and control file and log file in other directories.
    Thank you for your help.
    Bernard

    Hi,
    You're right, my problem is that the dropdown only show the location associated with the flat file location even if I have other file locations created in the design repository.
    The good news is that I have found the solution to solve the problem :
    1) Edit the file module and in tab "Data locations", add the locations you want to use for control file and log file.
    2) Open configuration window of the mapping and then the dropdown for properties Control File Location and Log File Location show new locations
    I have tested my mapping after changing those properties and it's working.
    Bernard

  • Storing degenerate dimension info in an OWB 10gR2 cube

    Hi,
    I'm looking to store "degenerate dimension" information in an OWB 10gR2 cube. Typically in a DW, I'd just add a column to the fact table to hold the information. However, in OWB 10gR2, I don't see any way to add a column to a "cube" object - everything appears to either have to be a dimension surrogate key, or a measure.
    Not sure the best way to proceed. We've coded all our ETL using the standard cube objects and letting OWB do all the surrogate key lookup, etc. automagically for us, so I'd hate to be forced to go back to manually loading the fact tables. Is there an easier way?
    Thanks,
    Scott

    Hi Scott,
    The problems I've run into with dimensions and cubes are:
    Dimensions abort if there are many roles - about 4 is the limit. This is very bad for the time dimension which should have 100s of aliases. Unfortunately I can't use the Time dimension wizard because we require ISO-Weeks. My workaround is to create several Time dimensions manually and assign 4 roles to each.
    Naming - when I create several time dimensions with 4 roles each (see above), in the BI layer, the foreign keys in cubes are always named something like time_dim, time_dim_1, etc rather than named for role names. I have to manually rename them in tables and then when I deploy BI objects, manually rename them again in Discoverer Administrator.
    Redeploying just about anything is broken. Table upgrade plans are invalid (even after running the grant scripts that support recommended), Redeploying BI objects runs successfully but if you read the job output, it does nothing since the objects already exist - again, the upgrade option does nothing.
    Column ordering is random when deploying objects so I've taken to sorting alphabetically for our BI objects. Not ideal by any means.
    As for the time savings with lookups, I don't save nearly that much. Due to many composite keys in our source systems, I assign surrogate keys in our staging area. These become the "business keys" in our DW layer and consequently I end up doing lookups against the staging MAP tables - really no more or less difficult than looking up dimension keys. That is more a design choice than anything and may just be my "Kimball" habits dying hard.
    I'm encouraged to hear that you are having success. I chose to utilize the Dimensions and Cubes and so far am sticking with it. I'm hoping that there will be patches and/or point releases to OWB soon!

Maybe you are looking for