EIF Export/Import Only Metadata

The following export statement 'export' entire AW with data. And import also imports everything.
exec dbms_aw.execute('export all to eif file ''MYDIR/TEST_OLAP.eif'' api');
exec dbms_aw.execute('import all from eif file ''MYDIR/TEST_OLAP.eif'' api');
Can I only export and import the metadata(like we do XML template) using commands like above?

Just learned... Try below.
jarname_ is the name of the AWM jar. e.g. awm11.2.0.2.0.jar
user is the name of your user. e.g. TESTOLAP
password is the password for your user
url is the url for a node in your RAC cluster. e.g. jdbc:oracle:thin:@myserver:1521:orcl
filename is the name of the XML file to create. e.g. testolap.xml
java -classpath jarname_ oracle.olapi.metadata.util.ExportXML -user user -password password -url url > filename
The java version should be "1.6.0_24".

Similar Messages

  • Exporting/Importing Transformation metadata

    Hello All,
    I have a custom written package which we use as a post-mapping process.
    I compile this package in the database external to OWB and then I import the definition into OWB. Where it becomes a transformation.
    We are currently in Dev and I now want to migrate to Test.
    So I tried to export the metadata for this package so I can import it into the Test Design Center. This is because I want everything contained in OWB.
    The export appears to work but when I import it into Test (which also seems to work) and try to generate the code it produces an empty file.
    Is it possible to export and import the metadata of a custome transformation? If so are there any particular options I should use?
    I'm sorry this seems to be a basic task but I can't find anything in the documentation and I wondered if anyone else had come across it.
    Thanks in advance.

    Hi,
    you cannot redesign a package with an import. You will only get the package header, not the body. You must create the custom transformation in the design center and then deploy it to the target database - not the other way round.
    Regards,
    Detlef

  • Export/Import integrator metadata between instances

    Hi all
    We have hit recently a situation with some customers who would like to migrate integrator related metadata from one instance to another (integrator, components, mappings, layout, parameter list).
    They are doing this using FNDLOAD. For example
    Download phase on the source.
    FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bneint.lct XXCOHR_Integrators.ldt BNE_INTEGRATORS INTEGRATOR_ASN="XXCOHR" FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bnemap.lct XXCOHR_mapping.ldt BNE_MAPPINGS MAPPING_ASN="XXCOHR" FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bnelay.lct XXCOHR_Layouts.ldt BNE_LAYOUTS LAYOUT_ASN="XXCOHR" FNDLOAD apps/apps 0 Y DOWNLOAD $BNE_TOP/patch/115/import/bnecont.lct XXCOHR_bnecont.ldt BNE_CONTENTS CONTENT_ASN="XXCOHR"
    Upload phase on the target.
    FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bneint.lct XXCOHR_Integrators.ldt FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bnelay.lct XXCOHR_Layouts.ldt FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bnemap.lct XXCOHR_mapping.ldt FNDLOAD apps/apps 0 Y UPLOAD $BNE_TOP/patch/115/import/bnecont.lct XXCOHR_bnecont.ldt
    The problem is that after trying to create a document using the new BNE elements they are getting various errors.
    No parameter list definition at parameter list idor No Mappings exist for the specified Content.
    I have had a look at some patch delivering integrators via the same LCT files , and the unified driver has for example the following sequence which is executed during the patch
    exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfcmp.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bnecomp.lct @PAY:patch/115/import/D/pyinfcmp.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
    exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfcnt.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bnecont.lct @PAY:patch/115/import/D/pyinfcnt.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
    exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfint.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bneint.lct @PAY:patch/115/import/D/pyinfint.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
    exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinflay.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bnelay.lct @PAY:patch/115/import/D/pyinflay.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
    exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfmap.ldt &ui_apps 0 YUPLOAD @BNE:admin/import/bnemap.lct @PAY:patch/115/import/D/pyinfmap.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
    exec fnd bin FNDLOAD bin &phase=last+1 checkfile:pay:patch/115/import/D:pyinfpar.ldt &ui_apps 0 Y UPLOAD @BNE:admin/import/bneparamlist.lct @PAY:patch/115/import/D/pyinfpar.ldt - UPLOAD_MODE=NLS WARNINGS=TRUE
    I couldn' find anywhere this process being documented in an official document or Note.These customers have used some external non-oracle references fordoing so.
    Is there anywhere a document giving more information on how this export/import is supposed to work?
    Please reply to me directly as I am not part of this mailing list.
    Thank you and best regards,
    Dan

    Looks like you have not transferred your parameter list. Please use following code to download and upload your parameter list.
    Download
    FNDLOAD apps/$FNDPWD 0 Y DOWNLOAD $ BNE_TOP / admin / import / bneparamlist.lct GENERAL_201.ldt BNE_PARAM_LISTS INTEGRATOR_ASN = "HX" INTEGRATOR_CODE = "GENERAL_201_INTG"
    Upload
    FNDLOAD apps/$FNDPWD 0 Y UPLOAD $BNE_TOP/admin/import/bneparamlist.lct GENERAL_201.ldt
    For mapping there is a possibility that you might have migrated wrong content. You need to migrate content which is none instead 'text'
    HTH

  • Is it possible to export/import only a page of an application?

    Hi,
    I tried to export one page of an application and this works correctly;
    then I import the same page in another application without problem, but when I try to install the page I obtain an error.
    Is this a bug?
    Can anyone help me?
    Thanks.

    After doing the import of the page (page2) successfully in a new application (application2), when I click on the button Install page, I have this error:
    File is not a valid HTML DB export file
    In effect, if I check the pages within the application2, there is not page2.
    I hope I have been clear enough

  • Bug in Export/Import of Metadata

    I have an image (freshly imported; DNG, converted from NEF) containing the keyword "Großbritannien" which is part of the keyword-hierarchy
    Welt
      Europa
       Großbritannien
    The image is developed to be Black and White.
    To get GPS-Info into the IPTC-fields, I
    1. In LR: Metadata - Save Metadata to file (just to be sure everything is written into the file; "Automatically write to XMP" is turned on)
    2. Open the image in GeoSetter (but all this applies if I don't use GeoSetter but e.g. apply "Recover Edges" to the dng-file) and save GPS-Information into the IPTC-Section of the file
    3. In LR: Metadata - Read Metadata from file
    In LR2, I now had the B&W image with keyword "Großbritannien" and GPS-information was filled.
    In LR3, the image is now coloured instead of B&W (develop history says "Einstellungen zurücksetzen", should be "reset to default" in english) and it has the keywords "Europa, Großbritannien, Welt" which are now single new entries despite being part of the hierarchy mentioned above.
    GPS-info is OK.
    WinXP, LR3 trial.

    ExifTool (used in GeoSetter) is reporting errors when writing data back to LR3 processed files.
    This is new to the latest version of GeoSetter, which uses a newer version of ExifTool.
    According to Friedemann Schmidt from GeoSetter:
    "[LR3] contains a bug that results in an incorrect written Creator in the metadata (list type 'bag' instead of 'seq'). That's why ExifTool (>= 8.26) now gives a warning. In prior versions of ExifTool, the Creator has been added again in the correct way. But the the Creator existed twice then in the XMP data and Lighroom didn't recognize nearly all metadata anymore after importing it again...
    In short: You can ignore this warning ;-) Your image data still contains the wrong metadata (written by Lightroom 3), but it doesn't contain the data twice anymore after saving with ExifTool 8.26 (GeoSetter 3.3.60).
    As far as I know this problem will be solved in the next update of Lightroom 3..."
    Also from Friedemann:
    " One more remark: If you used GeoSetter 3.1.20 together with Lightroom 3, after reimporting the metadata to LR 3 maybe your development settings of the images have been reset. Please check this! The deveopment settings still exist in the development protocol and you have to go one step back for each image..."
    This seems to cover the problem first reported in this thread with the picture reverting back to Color.
    If the metadata is wrong and we don't run GeoSetter to fix it, are there other implications?
    Does anyone know if this potential metadata error has been reported to Adobe so that LR3 can be fixed?

  • Export/import  Scenarios

    How to export scenarios in oracle Data Integrator from project.
    is there any way to do this .I do not want to import/export actual project contents like procedure,interfaces and packages instead i want export/import only scenarios
    at a single strech(entire project)
    Thanks
    prasanna

    Hi Prasanna,
    Yes you can export/import scenario by right clicking on the generated scenario and say Export. It will export that scenario as a XML file at your desired dir, from there you can again import it back by right clicking on scenario and say import scenario.
    Thanks,
    Guru

  • Importing the METADATA ONLY using DBMS_DATAPUMP

    Hi DBAs,
    Using the DBMS_DATAPUMP , how can I import the metadata only for a particular table . Also I dont want to import any associated INDEXES and TRIGGERS. I have the following codes but it is trying to import every thing. Also if the table exist, it is not importing the METADATA rather erroring out.
    handle1 := DBMS_DATAPUMP.OPEN('IMPORT','SCHEMA', 'QAXDB.WORLD');
    DBMS_DATAPUMP.METADATA_FILTER(handle1, 'SCHEMA_EXPR', 'IN (''HR'')');
    DBMS_DATAPUMP.SET_PARAMETER(handle1, 'INCLUDE_METADATA', 1);
    Thanks
    -Samar-

    See the below link,
    http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_datpmp.htm
    Hope this helps,
    Regards,
    http://www.oracleracexpert.com
    Click here for [Cross platform Transportable tablespace using Datapump|http://www.oracleracexpert.com/2009/08/transportable-tablespace-export-import.html]
    Click here to learn [Oracle data pump export/import with examples.|http://www.oracleracexpert.com/2009/08/oracle-data-pump-exportimport.html]

  • Metadata export/import to other BI tools?

    Metadata export/import to other BI tools?
    Hi ,
    I am using SQL DM 3.0.0.665. I need your thoughs on following.
    As we build our logical/physical models in SQL data Modeler, we create our metadata for our attributes/columns.
    After creating our physical model, other BI and reporting tools acquire access to the physical tables. Each tool has a process of creating their reporting layer and able to bring the tables/columns into reporting layer. It shows the column names as it is. It is not business friendly.
    Do we have a mechanism to export attribute business names as meta data of DB tables?
    If we define the meta data as part of physical model using modeling tools such as Oracle SQL Developer or ERWIN, will we able to import those into BI tools as report elements meta data?
    Where can I find details?
    How do we do that?
    Thanks in helping us out.

    Hi,
    there is no problem if you are building reports on top of our reporting repository - table DMRS_MAPPINGS holds information for pairs - (entity- table), (attribute-column)...., and you can take implementation and business name.
    Exchange to BI tools - you need to know how particular BI tool can recognize and link implementation and business names and then you can use transformation script in order to provide required information. There are examples on this forum how to deal with files and database connection using transformation script.
    Philip

  • Best practice metadata export/import  for WebCenter portal

    Hi
    I'm using JDeveloper to build the WebCenter portal. When I let's say register a portlet producer along with my portal, the information about it is stored in the metadata. In case I want to move my portal from the integrated WLS which JDeveloper provides to another WebLogic server with WebCenter installation - steps which I need to do are:
    1) Export the metadata from JDeveloper
    2) Import metadata to my target Weblogic server
    3) deploy the application
    Am I missing something?
    To export/import metadata from JDeveloper to another Weblogic (equipped with WebCenter) server I should use the WLST script, right?
    Thanks

    A little correction: IAS Version is Oracle9i Application Server Release 1 version 1.0.2.2.2

  • Importing only the metadata

    Hi,
    I have a full database dump and I would like to import only the metadata, i.e., only the objects structure.
    My database is an Oracle 8i versioned. I used the following:
    imp system file= log= full=y rows=n
    kindly let me know if I am wrong or is there any other way to do this.
    With the above statement only the schemas are created but there are no objects at all.

    rp0428 wrote:
    Did you specify TABLES=* to import all tables?import operates in 1 of 3 modes
    a) FULL=Y
    b) OWNER=<schema_name>
    c) TABLES=
    & they are mutually exclusive

  • Export/import OWB (10.1 and PARIS) metadata problems

    I am attempting to import an OWB 10.1–exported map into an OWB 10.2/PARIS repository .. this failed as follows from the Paris Design Center menu bar ...
    Design – Import – Warehouse Builder Metadata and specify a previously exported OWB 10.1 map. I receive the following message … ”Metadata version is not compatible with you current repository version. Upgrading the file is required to import your metadata”
    … Selecting ”UPGRADE” yields the following …
    Upgrade started at Jul 25, 2006 12:02:05 PM
    Preloading objects from release 9.2
    Upgrading objects from release 9.2 to 10.0
    Project "SIRR_DATA_CONVERSION"
    "Error occurred importing from file "C:\MKS\ConfigurationMgmt\OWB\Unit Testing\Build 1.13\Client Account\OWBC_ALS_CLI_CLIENT\OWBC_ALS_CLI_CLIENT.mdl".
    CNV0002-0025(ERROR): Unexpected error occurred. Upgrade terminated. See log file C:\MKS\ConfigurationMgmt\OWB\Unit Testing\Build 1.13\Client Account\OWBC_ALS_CLI_CLIENT\OWBC_ALS_CLI_CLIENT_10_0_upgrade.log for details. Please contact"
    The log contained over 16000 lines of info associated with mapping parameter/mapping parameter properties/property values, groups and finally, before failing, mappingparameterconnection --> mappingparameterconnection .. I can email the log if anybody is interested in taking a look.
    Two things with error above .. I do not have a 9.2 map (seems the upgrade is assuming a 9.2 map) but a 10.1 map .. and the error message seems to be truncated after ”Please contact”
    any advice on importing OWB 10.1 metadata(maps) into OWB PARIS ? as I am trying to create business case for upgrading from OWB 10.1 to PARIS.

    There is a similar issue logged in our Support database relating to this type of problem. The bug (ref number 5309802) has some workarounds relating to issues within an MDL file relating to non-unique IDs and blank properties for certain objects.
    The log file should tell you exactly where the problem objects are located, row and column reference. If you could open a TAR with Oracle Support and send them the log file and the associated MDL file they should be able to organize a fix for you.
    If you want to try this yourself then make a backup of the MDL file. Next open the MDL file using Winzip and extract the two files within the MDL file. The larger of the two files is in fact an XML file. Open this file in a text editor that shows line and column numbers. Now refer back to the log file and find the error messages from that file and cross reference row/column numbers within the XML file and see if the error makes sense to you. If it does, correct the error and then rezip everything back into an MDL file and try importing the MDL file again.
    Alternatively you may want to leave this to Oracle Support to manage for you.
    Hope this helps
    Keith

  • Can data pump only export/import views also.

    Hi
    Can anybody tell me how to export or import only tables and views through data pump.

    You can use include parameter.
    expdp userid=scott/tiger include=table include=view directory=DATAPUMP2 dumpfile=Only_Table_View.dmp
    impdp userid=scott/tiger dumpfile=only_table_view.dmp include=view include=table directory=datapump2

  • EXPORT full database only METADATA

    how to export only metadata of database with out user entered values.
    i want the database with same metadata is it possible to clone only target database metadata.

    Sure - u can use expdp/impdp with CONTENT=METADATA_ONLY option or else exp/imp with rows=n
    http://www.oracle-base.com/articles/10g/oracle-data-pump-10g.php
    ~Y

  • Importing only tables from full export

    hi,
    our database is going to get live..
    Oracle 10GR2
    Windows 2003.
    i have full expdp dump file...
    i just want to import only tables from that dumpfile..
    how can i do that..
    there are around 1059 tables...
    searched over the net but did not find anythiing..
    your help is needed....
    thank you ..
    wating for your

    thnks for the replay..
    the schema is different in which the tables needs to be imported.
    but this schema in which tables needs to b imported contains the same number of tables with same strutures.
    thanks.

  • Migrate Database- Export/Import

    Hi,
    I need to migrate an Oracle database 9i from Sun Solaris to Linux. The final target database version would be 11g.
    Since this is a 9i database, I see that we have only option of export and database. We have around 15 schemas.
    I have some queries related to it.
    1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?
    2. Can we perform export in Oracle 9i and use datapump import on targert 11g?
    3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?
    Since there is a database version different I dont want to touch sys, system schema objects.
    Appreciate your thoughts.
    Regards
    Cherrish Vaidiyan

    Hi,
    Let me try to answer some of these questions you queried for:
    1. If I perform a export with full=y rows=y, Does it export Sys, System Schema objects also?Export won't export sys objects. For example, there are tables in sys, like obj$ that contain information for other metadata objects, like scott.emp, etc. This is not exported becuase when scott.emp is exported, the data from obj$ is essentially exported that way. When the dumpfile is imported and scott.emp is recreated, the data in sys.obj$ will be restored through the create table statement. As far as the SYSTEM schema is concerned, some objects are exported and some are not. There are tables in system that contain information about queues, jobs, etc. These will probably not make any sense on the target system so those types of tables are excluded from the export job. Other objects make sense to export/import so those are done. This is all figured out in the internals of export/import. Thre are other schemas that are not exproted. Some that I can think of are DMSYS, ORDSYS, etc. This would be for the same reason as SYS.
    2. Can we perform export in Oracle 9i and use datapump import on targert 11g?No, the dumpfiles are formatted differently. If you use exp, then you must use imp. If you use expdp, then you must use impdp. You can do exp on 9i and imp on 11g with the dumfile that was created on 9i.
    3. What is the ebst approach - a) to perform schema by schema export or b) to perform a full database export with exp / file=xxx.dmp log=xxxx.log full=y?This is case by case decision. It depends on what you want. If you want the complete database moved, then I would personally think that a full=y is what you would want to do. If you just did schema exports, then you would never export the tablespaces. This would mean that you would have to create the tablespaces on the source system before you ran imp. There are other objects that are not exported when a schema level export is performed that are exproted when a full is performed. This information can be seen in the utilities guide. Look to see what is exported when in user/schema mode vs full/database mode.
    Since there is a database version different I dont want to touch sys, system schema objects.This is all done for you with the internal workings of exp/imp.
    Dean
    Edited by: Dean Gagne on Jul 29, 2009 8:38 AM

Maybe you are looking for