Export km repository

hi i have doubt can we export km repository
if yes how can we achieve that

Vani,
There are some things to watch for when you use the webdav method of transporting km content. The most important is that It won't bring metadata for the documents, or permissions... I have found that ICE works much better for maintaining documents as it brings the majority of the information we want over.
There is no way that i have found to move the layoutsets other then like mentioned... another thing we should all harp on SAP about is making more of these types of objects either work with ICE or simply transportable throught the normal method! It is interesting to me that very little focus has ever been put on the KM development!
Message was edited by:
Trevor Carlow

Similar Messages

Warning on Exporting DAC Repository Metadata

After finishing export DAC repository metadata, we got some warning as following:
W_ETL_SA: 26 objects
31705 INFO Wed Nov 11 11:15:12 CST 2009 Exporting entity W_ETL_SA for application EBS 11.5.10.W
31706 INFO Wed Nov 11 11:15:12 CST 2009 Moved W_ETL_SA: 26 objects
31707 INFO Wed Nov 11 11:15:12 CST 2009 Exporting entity W_ETL_TABLE for application Universal
31708 WARNING Wed Nov 11 11:15:12 CST 2009 Mismatch between the number of records in the object reference table and objects
There are 14 warning of all.
Does it mean something wrong with DAC reposritory?
Roger

Hi,
I have spoken to Oracle about this previously, apparently these warnings are not important and are nothing to worry about, see here:
[http://obiee-tips.blogspot.com/2009/09/dac-importexport.html|http://obiee-tips.blogspot.com/2009/09/dac-importexport.html]
They still worry me a bit though...
Regards,
Matt

Issues in exporting/importing repository fromInformatica version 8.6 to 9.1

Hi There,
I completed Informatica 9.1 hotfix2 server and client installation successfully in a seperate computer(system).
Also configured repository and integration services in version 9.1.
Now I need to export Informatica 8.6 repository and import into Informatica 9.1.
Are there any steps which I need to follow to complete this process?
Can someone pls help me with these steps.
Thanks in advance,
Rag

Thanks Srini.
I tried to restore version 8.6 repository into version 9.1 repository.
I got the below error log.
Is it not possible to restore 8.6 repository into 9.1? Any ideas pls....
My email and cell numbers are: [email protected], 9652227856
-------------------Log-------------------------------------------------------------------------------------------------------------------
Rep_57106 repository operation error.
Restore Contents operation on repository [REP_TEST91] started at 01/07/2013 11:08:25.
Restoring repository contents from file [C:\Informatica\9.1.0\server\infa_shared\Backup\DEV_INFA_REP_03JAN2013.rep].
domain name: DNE_INFA_TEST
Backup file repository version : 179     Current repository version : 181
File backup version : 10     Current backup version : 10
Backup file is valid : Yes
Backup file code page id : 106     Current code page id : 106
This backup file is from a different version of the Informatica Repository.
Unable to restore Repository.
Restore Contents operation on repository [REP_TEST91] ended at 01/07/2013 11:08:25. Elapsed time is 0:00:00.
Thanks,
Raghu

Problems in export / import repository

Hi there,
I'm trying to export/import a repository.
The first trouble is: I export the topology, but when I import it nothing is imported (no error messages).
I resorted to manually reconfiguring the topology
The second and worse trouble is: I exported the project and the models, then I imported the project (successfully)
but when I tried and import the models I got some error messages related to missing data (referential integrity)
Any help is warmly appreciated
Regards
Andrew Florit

I've got the same problem "I export the topology, but when I import it nothing is imported (no error messages)."
What could be the solution?
Thanx

Error while trying to upgrade ODI repository using export/ import

Hi,
I am getting below error while trying to import an ODI project from dev environment into my QA environment which has an older version of project.
com.sunopsis.core.SnpsNotConsistentSynonymImport: ODI-10013: This import action has been cancelled because it could damage your repository. This is due to an SNP_COL object that has object identifier 13712007 that is greater than that for the current SNP_COL id sequence. Importing this object would lead to primary key violations in the future.
at com.sunopsis.dwg.DwgObject.doImport(DwgObject.java:6041)
at com.sunopsis.dwg.DwgObject.doImport(DwgObject.java:5781)
at com.sunopsis.repository.manager.RepositoryManager.importObjectsUsingDoImport(RepositoryManager.java:5194)
at com.sunopsis.repository.manager.RepositoryManager.treatObjectListGeneral(RepositoryManager.java:3587)
at com.sunopsis.repository.manager.RepositoryManager.workRepositoryImport(RepositoryManager.java:4002)
at com.sunopsis.repository.manager.RepositoryManager.workRepositoryImport(RepositoryManager.java:4174)
at com.sunopsis.graphical.dialog.SnpsDialogImportWork$1.run(SnpsDialogImportWork.java:519)
at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:656)
at java.lang.Thread.run(Thread.java:619)
Did anyone face this error? What is causing this error? What should be done to resolve this error?
Edited by: 854415 on Oct 18, 2011 4:51 AM

Hi
Did you follow below approch
Goto Topology> File Menu>Export>Export Master Repository in ZIP format
File Menu>Export>Export Logical Topology in ZIP format
In Designer, go to File menu>Export>Export Work Repository in ZIP format
Quit from old ODI instance
Login into New ODi instance
Goto Topology> Import>Import Master Repository in ZIP format (please select INSERT and UPDATE Mode option from dropdown list)
Import>Import Logical Topology in ZIP format (please select INSERT and UPDATE Mode option from dropdown list)
In Designer Import>Import Work Repository in ZIP format (please select INSERT and UPDATE Mode option from dropdown list)
Note: Once it is done please change the Work repository ID on New ODI instance
Regards,
Phanikanth

Export repository to filesystem?

Repostet at How to export repository to file system?
Hello,
within my bachelor thesis I am engaged in parsing ABAP Objects to calculate different code metrics. The analysis tool and many of the known parser-apis do require source-files at the file system layer.
As SAP stores everything in a DB, I wonder if there is a way to export the repository to the file system. And if this is not possible, is there another practicable way to access the source code?
Another point is: Does anyone know a source for a complete grammar (like ebnf or so) for ABAP Objects? that could make my life quite a lot easier...
mfg
- clemens heppner
Edited by: clemens heppner on May 5, 2008 10:26 AM

Thanks for your advice! I've written this report:
START-OF-SELECTION.
DATA: source TYPE REF TO cl_oo_source,
source_tab TYPE seop_source_string,
classname TYPE seoclskey VALUE 'CL_OO_SOURCE'.
CREATE OBJECT source EXPORTING clskey = classname.
* Copy source->SOURCE table because gui_download( ) needs a changeable
* argument and source->source is read-only.
source_tab = source->source.
cl_gui_frontend_services=>gui_download( EXPORTING filename =
'c:\source.ao' CHANGING data_tab = source_tab ).
But that approach has some serious drawbacks:
I have to save each class one by one (is there a way to automate that? P.e. find all classes in one package?)
I can not access the code of reports and such because cl_oo_source requires a classname.
Is there another way or an extension to this one, to solve those problems?
Thanks,
- clemens

How to export repository to file system?

Hello,
within my bachelor thesis I am engaged in parsing ABAP Objects to calculate different code metrics. The analysis tool and many of the known parser-apis do require source-files at the file system layer.
As SAP stores everything in a DB, I wonder if there is a way to export the repository to the file system. And if this is not possible, is there another practicable way to access the source code?
Another point is: Does anyone know a source for a complete grammar (like ebnf or so) for ABAP Objects? that could make my life quite a lot easier...
mfg
- clemens heppner

Thanks for your advice! I've written this report:
START-OF-SELECTION.
DATA: source TYPE REF TO cl_oo_source,
source_tab TYPE seop_source_string,
classname TYPE seoclskey VALUE 'CL_OO_SOURCE'.
CREATE OBJECT source EXPORTING clskey = classname.
* Copy source->SOURCE table because gui_download( ) needs a changeable
* argument and source->source is read-only.
source_tab = source->source.
cl_gui_frontend_services=>gui_download( EXPORTING filename =
'c:\source.ao' CHANGING data_tab = source_tab ).
But that approach has some serious drawbacks:
I have to save each class one by one (is there a way to automate that? P.e. find all classes in one package?)
I can not access the code of reports and such because cl_oo_source requires a classname.
Is there another way or an extension to this one, to solve those problems?
Thanks,
- clemens

How can I move the ODI Work Repository from one server to another server?

How can I move the ODI Work Repository from one server to another server?

Hi,
If you would like to move your source models, target models and project contents from Work repository 1 to another work repository.
I.e. Dev. server to Prod Server.
1. Firstly, replicate the master repository connections i.e. with same naming conventions manually
2. Go to Dev. Server work repository -> File Tab -> Click on Export work repository (save it in a folder)
3. After exporting, you can view the xml files in the folders.
4. Now, Open the Prod. server and make sure you already replicated mas. rep. details.
5. Now, right click on model and import source model in synonym mode insert_update (select source model from the folder where your xml file located)
6. Similarily, import again target then Project.
Now, check. It should work.
Thank you.

Reg: importing/exporting repositories problem

Hi all,
I done all the exports from development in below vice versa:
from topology:
export master repository
export topology
export logical topology
export execution environment
from security
export security settings
from designer
export work repository
all are in .zip file formats only.
i created 2 new schams in production db like impmaster for master repository and impwork for work repository
then next
i created one new login name example produtionmastr
1)after that i imported master repository from import master repository winzard.
2)it imported sucess fully i got all technologies,physical servers,physical schems,logical schemas,agents,contexts also.
3)next i tried to import topology,logical topology and execution environment it takes time but nothing will be impoted. (my quwstion is what is the reason for we
again import topology logical topology again,when the time import master repository only we are getting all the things in topology.then what is use for this options.)
4)next think i created one work repository in topology manager with different id from development
5)i created login name for work repository and i login to designer.
6) i imported work repository from zip file using synonym insert mode. imported success.
7)i changed all the physical paths in physical data servers. every thing fine.
8)but i am getting problem with agent.previously i am working with odi 10.1.3.
error is:
oracle.odi.runtime.agent.invocation.InvocationException: ODI-1221: Unable to restart session 11050: session is not found in work repository WORKREP1.
     at oracle.odi.runtime.agent.invocation.RemoteRuntimeAgentInvoker.invoke(RemoteRuntimeAgentInvoker.java:260)
     at oracle.odi.runtime.agent.invocation.support.InternalRemoteRuntimeAgentInvoker.invokeStartSession(InternalRemoteRuntimeAgentInvoker.java:171)
     at com.sunopsis.graphical.dialog.SnpsDialogExecution.runStartSession(SnpsDialogExecution.java:1972)
     at com.sunopsis.graphical.dialog.SnpsDialogExecution.doVariableExecuter(SnpsDialogExecution.java:1340)
     at com.sunopsis.graphical.frame.edit.EditFrameSnpVar.handleRefreshVariableAction(EditFrameSnpVar.java:818)
     at com.sunopsis.graphical.frame.edit.EditFrameSnpVar.access$6(EditFrameSnpVar.java:796)
     at com.sunopsis.graphical.frame.edit.EditFrameSnpVar$1.actionPerformed(EditFrameSnpVar.java:346)
     at com.sunopsis.graphical.component.toolbar.OdiTextAreaToolbarAction.executeAction(OdiTextAreaToolbarAction.java:146)
     at com.sunopsis.graphical.component.toolbar.AbstractOdiToolbarAction.actionPerformed(AbstractOdiToolbarAction.java:203)
     at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995)
     at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2319)
     at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387)
     at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242)
     at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:236)
     at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:274)
     at java.awt.Component.processMouseEvent(Component.java:6289)
     at javax.swing.JComponent.processMouseEvent(JComponent.java:3268)
     at java.awt.Component.processEvent(Component.java:6054)
     at java.awt.Container.processEvent(Container.java:2042)
     at java.awt.Container.dispatchEventImpl(Container.java:2099)
     at java.awt.Component.dispatchEvent(Component.java:4483)
     at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
     at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4238)
     at java.awt.Container.dispatchEventImpl(Container.java:2085)
     at java.awt.Window.dispatchEventImpl(Window.java:2479)
     at java.awt.EventQueue$1.run(EventQueue.java:601)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:98)
     at java.awt.EventQueue$2.run(EventQueue.java:618)
     at java.awt.EventQueue$2.run(EventQueue.java:615)
     at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
     at java.awt.EventQueue.dispatchEvent(EventQueue.java:614)
     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:270)
     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:175)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:170)
     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:162)
     at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
9)in 11g odi agent creation was totally different all configurations need to odiparams.bat.
10)my doubt can i need to update all the repository names in odiparams.bat file
11)or we can reuse the one agent to all repositories why because in 11g we are giving all reps names in odiparams.bat file.
please share your solutions
Regards,
Surya

3)next i tried to import topology,logical topology and execution environment it takes time but nothing will be imported. (my quwstion is what is the reason for we
again import topology logical topology again,when the time import master repository only we are getting all the things in topology.then what is use for this options.)
Ideally i would suggest when you are importing for the first time you can use the Import Master Repository wizard and from next time if any small changes has then import those individual ODI Object.
You don't have to repeats those individual import once the Master Repository Import is successful.
Reg Agent Error You can create an Agent manually in the your new Topology.
I believe you have upgraded from 10g to 11g . In that case all your Master Rep url and credentials might change and so the old odiparams might not work .Please update odiparams accordingly.

.tpz files naming convention / export from PI 7.0

Hi,
When I export the repository or Directory content from PI 7.0 the naming convention PI gives its own naming convention. Starting wit XI3_0 * .tpz
Why does it start with XI3_0*.tpz for we have PI 7.0?
Do we need to change any Visual admin or exchange profile parameter to get the naming convention to PI7_0*.tpz
Thanks
Sachin

Hi,
The import and export functionality of XI 7.0 uses the expression 'XI 3.0' instead of 'XI 7.0' in all transport screens of the Integration Builder. Furthermore the name of XI 7.0 exports will always start with the prefix 'XI_3_0' and not 'XI_7_0'.
<b>Reason and Prerequisites</b>
The reason for this behaviour is that the transport code and format of XI 7.0 and XI 3.0 is identical.
<b>Solution</b>
There is no fix for the naming convention, but there is a positive consequence: XI 3.0 export files can be produced by XI 3.0 and XI 7.0 and can be imported into XI 3.0 and XI 7.0.
Refrence Note
Note 936254 - XI 3.0 Imports and Export in XI 7.0
Award points if helpful.
Thanks,
Tanuj

SRM MDM 3.0 BMECAT Repository Schema

Hello at all,
I have currently run the SRM-MDM 3.0 with the standard respository delivered as archive on the install CD. I still have created some data with the data manager and it runs all very well.
Now I want to import a catalog based on BMECat 1.2 standard. I Have the complex catalog data XML from the vendor Bechtle and the images folder for the articles.
When running the Import Manager there are many fields and tables in the source xml that do not excist in the destination hierachy (repository).
My question is how do I create a repository based on the BMECat 1.2 standard to import the vendor catalog xml ?
What I still tryed was. Creating a new repository. It's empty except of the standard table like Admin, Images, Products etc.
Than go to Transport -> Import Repository Schema -> choose the vendor XML
That doesn' work. I get the Error Message: "There are problems with the transport (XML) which prevent it from being processed"
I have learned that an XML schema data is described with the ending .xsd but when I try to import the databrowser looks for .xml endings.
Could someone please advice what's I have done wrong?
Thanks a lot.
Rico

Hi Rico,
I am not aware of BMEcat standard but in MDM terms you can take the backup of repository in two forms:
1. Archive/UnArchive -> If you want to move the repository from one MDM server to another i.e. from dev to QA then you can Archive the repository which creates the .a2a file and place the file in the Archives folder of MDM Server installation directory which can then be copied and moved to Archives folder of target MDM server and you can UnArchive it on that MDM server.
Archive = Repository Schema + Data
2. Export / Import Repository Schema -> With this method you can export the schema of the repository and create the new repository on some other MDM Server using Create Repository from Schema command. When you perform the export repository schema command, it will ask for the file name and path. You can then copy this schema file and place in the file system of another server.
Export / Import Repository schema = Repository Schema only
Regards,
Jitesh Talreja

Steps to be followed in Export/Import

Can anyone help me out defining the exact steps to be followed in exporting and importing the ODI objects?
I have exported the master and work repository. I created a new master repository by importing the zip file. I can see the architecture neatly imported into the topology. The problem starts when I try to import the work repository. It keeps throwing the integrity constraint error. I export/import folder-wise as the current work repository is pretty huge!!
It will be of great help if some one could explain the steps to be followed while export/import in ODI

Hi there,
It is typical of ODI to throw those errors, as the documentation is not quite comprehensive about how to do it.
Here are a few guidelines:
(i) Topology (master repository) should be exported n imported first. Then the models and finally the projects and the variables. Also, work repository export may not work if you try to export whole work repo at one go using File---->Export---->Work Repository !
So the best thing is File--->Export---->Multiple Export----> then drag all ur objects into the box and check the "zip" checkbox
Create separate zips for Models and separate for Projects and so on
And import Model zip before Project zip in your new repository
OR
(ii) Use database schema export and import. This has worked the best for us.
And I think it is the most flawless way of doing export import because you dont lose any objects and dont get any integrity constraint errors etc
Just export the master repository & work repository schemas and then import them in you new database

Import Repository Objects Question

Hello experts,
I am using a XI 3.0 SP13 development system. I export some repository objects under a certain namespace to a local file. Then I delete these objects and import the local file back into XI. Strange is, it shows the import is successful, i can see the object list in the "Display Transport" screen, but none of the objects are existing in the namespace.
Any suggestion to solve it ?
Thanks a lot !

1. Check if the user XIAPPLUSER is locked
2. Test connection for SAPSLDAPI & LCRSAPRFC in sm59
3. Maintain the URL for SLD in transaction SLDAPICUST.
Do SLDCHECK now.
If this doesnt work
1. Check if the user XILDUSER is locked. If not try to reset the password .If it is locked unlock it.
2. Then, in the exchange Profile http://sap02:50000/exchangeProfile, go to Connection tab and enter the password of XILDUSER again.

Upgrade 6.0 repository to 10g

How's the best way to accomplish the repository upgrade ?
I also have a 9i repository into which the 6.0 needs to be merged into at sometime...
Thanks

It is easy to see what version of the repository you have. Start any of the Designer client tools, connect to your repository, and choose the "Help" menu. Then choose "About". The Component labeled "Configuration" will be your Repository version. For a more detailed look, press the "System Info..." button. But if it is accessible with a 9i client, it is probably the version of the repository that goes with a 9i client - client and repository are very closely coupled - only the RAU can usually connect to a repository that doesn't match the client.
If you use RAU from 9i to look at your current repository, if the "Upgrade" button is grayed out, then RAU believes that your current repository is in fact the correct version for your 9i client. If so, do yourself a favor: Use "Check Requirements" and make sure that the EXECUTE_EXPORT parameter is pointed at the "exp" utility for the database version in which the repository is installed. If you don't have client software for this database, get it and install it in a separate Oracle Home. Then use the "Export" button in RAU to back up your repository.
If you connect to the current repository with your 10g client's RAU, that "Upgrade" button should be active, meaning that RAU is ready and able to upgrade that repository to the version that is compatible with your 10g client. Don't do that yet. First, you want to make a good backup of your current repository.
Now you have a decision to make. You say that you made a new repository instance on a 10g database. I don't think you really want or need a new repository. What you really want to do is upgrade your current repository. So I would go ahead and drop your new repository owner with the "CASCADE" option, to give yourself a clean slate. Now do you want to upgrade in place, or do you really want to move your repository to a new database? If you want to move to a new database, I would export the repository owner schema with "exp" outside of Designer using the "exp" version that matches the original database, then import it using the "imp" version that goes with the new database.
There is one problem that you may encounter when you do this. Later versions of the repository have four collection types created with the "CREATE TYPE" command - JR_NUM_LIST, JR_STR_LIST, SDD_ACC_PRIV_LIST, and SDD_SYS_PRIV_LIST. Object types have an associated object ID, that some versions of "exp" do not export properly. On import, the objects get created with a new object ID, yet when the data is imported, Oracle won't import it because the new object ID doesn't match the ID of the data being imported. The solution is to pre-create the schema for your repository owner, and pre-create these objects using the OID clause with the object ids that they had in the old repository. Then import with the "ignore errors" option.
Finally, connect to your repository with the 10g version of RAU and press the Upgrade button. Good luck, and let us know how it turns out.

Re: OVM Repository and VM Guest Backups - Best Practice?

Hi,
I have also been looking into how to backup an OVM Repository, and I'm currently thinking of doing it with the OCFS2 reflink command, which is what it used by the OVMM 'Thin Clone' option to create a snapshot of the virtual disk's .img file. I thought I could create a script that reflink's all the virtual disks to sperate directory within the repository, then export the repository via OVMM and backup all the snapshots. All the snapshots can then be deleted once the backup was complete.
The VirtualMachines directory could also be backed up in the same way, or I would have thought it would be safe to back this directory directly, as the files are very cfg files are very small and change infrequently.
I would be interested to hear from anyone that has any experience of doing a similar thing, or has any advise about whether this would be doable.
Regards,
Andy

yes, that is one common way to perform backups. Unfortunately, you'll have to script those things yourself. Some people also use the xm command to pause the VM for just the time it takes to create the reflinks (especially if there is more than one virtual disk in the machine and you want to make sure they are consistent).
You can read a bit more about it here:
VM Manager and VM Server - backup and recovery options
great article (in german but you can understand the scripts) about this http://www.trivadis.com/fileadmin/user_upload/PDFs/Trivadis_in_der_Presse/120601_DOAG-News_Snapshot_einer_VM_mit_Oracle_VM_3.pdf
and I have blogged about an alternative way where you clone a running machine and then backup that cloned (and stopped) machine
http://portrix-systems.de/blog/brost/taking-hot-backups-with-oracle-vm/
cheers
bjoern

Export km repository

Similar Messages

Maybe you are looking for