MDM 7.1.4 SP4 don't Export Repository Schema

Hi,
I am using SRM-MDM Catalog3.0 , MDM 7.1 SP04 , in console , to operate Export Repository Schema failed.
MDS log:
Could not transport expression because it contained a non-transportable element: 'Item Status [Approved]'
Assignment Code='Set_Status_Code13' of Table Code='MDMSRM_CATALOG_ITEMS' requires additional steps before transport.
how to solve?
thanks in advance
Jesse

Hi Jesse,
Please refer SAP Note: 1385073:
In the Note>Navigate to General>Note the following
1. A code field was added for Validations and Assignments. All repositories must undergo verify/repair before loading for
the first time in MDM 7.1 SP04 so that the added codes for Validations and Assignments are implemented.
2. Validations and assignments from previous versions that contain lookup values will need modifying before the repository schema can be transported as the lookup values in expressions will now internally include the lookup table ID in addition to the value itself. This change was made to ensure that expressions with lookup values are transported correctly.
In order to modify these expressions you will need to load the repository and delete all the referenced lookup values from
each expression and then add them back into the expressions. If you try to transport the repository schema before modifying
the expressions, you will receive a transport error and a message will be generated in the MDS.log stating the assignments or validations that need to be updated.
Regards,
Mandeep Saini

Similar Messages

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

Unable to export the Schema

Hi ,
7.1 SP 8
I am facing some problem while i try to extract the schema .
right click on the repository -> Transport -> Export repository schema .
i get an error called "This repository requires additional steps before transport . See MDS log for details ".
And the Log does not help much to analyse the issue it says -> "Attempt to create delta failed . RC exception caught 0x86020002".
Has any one tackled this error before .
I have tried the Verify and repair option as well but still not able to export the schema .
Regards,
VIgnesh
Edited by: Vag Vignesh Shenoy on Mar 6, 2012 3:22 PM

Hello Vineet,
Can you double check and confirm if we get the pop up where we accept and reject changes while Exporting the schema?
If i am not wrong we get the Pop Up while we Import the schema where we can accept or reject the Changes flowing into the current schema and it is there we face dependencies failure and Schema doesnot get imported.
Correct me if my understanding is wrong.
Rgds,
Prasad.

I'm trying to export a raw image from lightroom 5.6 to Photoshop cc 2014 2.1. I right click to export menu in lightroom as I've always done to export to Photoshop. Photoshop opens, but it can't open file, window opens to find a file to open. I'd like t

I'm trying to export a raw image from lightroom 5.6 to Photoshop cc 2014 2.1. I right click to export menu in lightroom as I've always done to export to Photoshop. Photoshop opens, but it can't open file, window opens to find a file to open. I'd like this to export my lightroom images to edit in photoshop as it has always been able to do for me. What fix do you recommend?

Hi Ashley Clavette,
The Initial view setting works perfectly when the file is opened in Acrobat after setting the desired Initial View.
When you upload the file onto Wordpress, and view it on that website in the browser...it might be using a different pdf handler program which might be causing this issue ( it would be helpful, if you could provide the screenshot) , however when you download the pdf again from wordpress server...and open in Acrobat/Reader...then what exactly happens ? Does the pdf opens in the desired Initial View setting?
Rahul

Crossfades don't export smoothly

Hi everyone,
I've got a large multi-track edit of a pipe organ recording. We've edited the piece with cross-fading different takes to make one succinct song. I've found though that once I'm satisfied with my cross-fades, they don't always playback smoothly in a consistent manner. I've found also that they don't export well. When I play a two-track mix of the piece for CD, the edits either don't play smoothly or they have little clicks and pops in them.
Is it a latency issue? Any suggestions as to how to get these to export play smoothly?
Your immediate assistance is greatly appreciated as we need to get a master out quickly for an event.
Message was edited by: HomeVideoStudio

No, they're each a second long or so. The timeline is merely zoomed out all the way out to show all the edits, which are crossfades into another take.
The creation of the crossfades are not the problem. Playing back the file is typically fine, the problem is exporting the mix. When the multitrack is mixed down to stereo, these transitions are very audible (clicks, pops, etc.) instead of the seamless transitions they should be.
Anyone know why this wouldn't export smoothly over these crossfades? It's never been a problem in Digital Performer or ProTools.
Your urgent response is appreciated. We've got to wrap-up this project.

Why is the version file smaller than the original file, although I didn't make changes in the file? And why is the keywords don't exporting with original files?

Hi! Why is the version file smaller than the original file, although I didn't make changes in the file? And why is the keywords don't exporting with original files?

Wild guess: you're using the the wrong export settings. You'll need to tell us more before we can help you - like the export settings you're usng, the size and format of the originals etc.

Don't export blank pages

Hi,
is there a "Don't export blank page" when exporting in PDF?
Thanks
Ben

Thank the Gods, no!
On several occassions, I cursed the engineer who thought it useful to include it into the Print dialog and to enable it by default.
Why would you not want to export blank pages? Disk space is cheap. (Oh alright, when pressed I could --maybe-- come up with a reason.)

SOS!! How to export a schema while the SYSAUX tablespace is offline?

Hello,
the SYSAUX for one of our productive database became corrupted and I had to take it offline in order to open the database. There is no way to recover it since there are missing archive logs from the sequence.
So I need to export a database schema which holds all the productive tables/indexes (there are no procedure, functions, packages, triggers,etc - just tables, constraints and indexes).
When I try to export the schema, I get the following error:
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Export done in UTF8 character set and UTF8 NCHAR character set
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user CMS31_ARMENTEL_SITE_N
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user CMS31_ARMENTEL_SITE_N
About to export CMS31_ARMENTEL_SITE_N's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
EXP-00056: ORACLE error 376 encountered
ORA-00376: file 3 cannot be read at this time
ORA-01110: data file 3: '/opt/data1/oradata/UTF8/sysaux01.dbf'
ORA-06512: at "SYS.DBMS_METADATA", line 1511
ORA-06512: at "SYS.DBMS_METADATA", line 1548
ORA-06512: at "SYS.DBMS_METADATA", line 1864
ORA-06512: at "SYS.DBMS_METADATA", line 3707
ORA-06512: at "SYS.DBMS_METADATA", line 3689
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
I've tried direct export, data pump (expdp) but with the same unsucessfull results.
Is there any way to use the export or expdp utility to get the actual data from a specific schema ?
Many thanks

Hello Harry and many thanks for your reply.
EXCLUDE is an option of expdp not exp. So I used expdp and get the following error:
expdp impexp/blabla dumpfile=SITE_N.dmp schemas=SITE_N exclude=CLUSTER:SITE_N
Export: Release 10.1.0.2.0 - Production on Tuesday, 29 January, 2008 20:56
Copyright (c) 2003, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
ORA-31626: job does not exist
ORA-31638: cannot attach to job SYS_EXPORT_SCHEMA_05 for user IMPEXP
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 377
ORA-39077: unable to subscribe agent KUPC$A_1_20080129205606 to queue "KUPC$C_1_20080129205606"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPC$QUE_INT", line 248
ORA-25448: rule SYS.KUPC$C_1_20080129205606$227 has errors
ORA-00376: file 3 cannot be read at this time
ORA-01110: data file 3: '/opt/data1/oradata/UTF8/sysaux01.dbf'
Different error (since now I use expdp) but for the same reason (SYSAUX is offline)
Regards
Argyris

Export of schema with space it its name

we have a schema named "Gestion Loaners" (note the space in schema name) in oracle 9iR2 database. i want to take schema level export but as there is space in schema name i am not able to do it using either escape char or using parameter file..
can anyone guide me pls
thx

It works if the Username is ALL CAPITALS. Couldn't get it work if the Username was Mixed Case
SQL> create user "PAVAN KUMAR" identified by pavan;
User created.
SQL> grant create session, create table to "PAVAN KUMAR";
Grant succeeded.
SQL> create table "PAVAN KUMAR".his_table (col_1 varchar2(5));
create table "PAVAN KUMAR".his_table (col_1 varchar2(5))
ERROR at line 1:
ORA-01950: no privileges on tablespace 'USERS'
SQL> alter user "PAVAN KUMAR" quota unlimited on USERS;
User altered.
SQL> create table "PAVAN KUMAR".his_table (col_1 varchar2(5));
Table created.
SQL>
ora10204>exp hemant/hemant owner=\"PAVAN KUMAR\"
Export: Release 10.2.0.4.0 - Production on Wed Nov 5 22:33:47 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user PAVAN KUMAR
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user PAVAN KUMAR
About to export PAVAN KUMAR's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export PAVAN KUMAR's tables via Conventional Path ...
. . exporting table HIS_TABLE 0 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.
ora10204>

Export Authorization schemes either in 4.0 or 4.1

Hi all,
I would like to export authorization schemes of an app. and import it in another env. I don't expect to create authorization schemes in env. like production. So, the required schemes are created in say for e.g. in dev and get exported just the schemes without being exported the whole app.
Is there anyway in either apex 4.0 or 4.1? If not, Is there any work around?
Thanks in advance
movva

Hi,
You can export , but I have not managed import those to different app.
I get
These components were exported from a different application or from an application in a different workspace. The components cannot be installed in this application.Workaround is export whole app and import it to workspace where is app where you like copy authorization schemes.
Then in target app go create new authorization schema and select As a Copy of an Existing Authorization Scheme. Then select from witch app you copy schema.
When you have copy all needed drop source app.
Regards,
Jari
http://dbswh.webhop.net/dbswh/f?p=BLOG:HOME:0

Export a schema

Hello
i got the below error , when i try to export the schema from Database 11g using exp utility 10g .
its successfuly exported if i export it using exp utility 11g , but i need it using exp utility 10g so i can import it to oracle db 10g .
Export: Release 10.1.0.4.2 - Production on Mon Sep 27 11:37:47 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in AR8MSWIN1256 character set and AL16UTF16 NCHAR character set
Note: indexes on tables will not be exported
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user CPI_STG
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user CPI_STG
About to export CPI_STG's objects ...
. exporting database links
. exporting sequence numbers
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
EXP-00056: ORACLE error 1455 encountered
ORA-01455: converting column overflows integer datatype
EXP-00000: Export terminated unsuccessfully

Using expdp you can export to a lower version.
You should be able to use impdp 10g to import that data.
Obviously you can also use the NETWORK_LINK parameter in the 10g command line to have impdp connect direclty to the 11g database.
I wouldn't use exp and imp, and they are also officially obsolete.
Sybrand Bakker
Senior Oracle DBA

How to export one schema

hi,
I want to do export from the database with only one schema, do anyone know what is the command.
Amy

Here you have a complete example to export/import a schema.
[oracle@ozawa bin]$ export ORACLE_SID=LQACNS1
[oracle@ozawa bin]$
[oracle@ozawa bin]$ sqlplus /nolog
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Mar 4 09:43:57 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
SQL> conn / as sysdba
Connected.
SQL>
SQL> create user joelp identified by joelp
2 default tablespace users
3 temporary tablespace temp;
User created.
SQL>
SQL> grant connect, resource to joelp;
Grant succeeded.
SQL>
SQL> conn joelp/joelp
Connected.
SQL>
SQL> create table t1 ( c1 number );
Table created.
SQL> insert into t1 values (10);
1 row created.
SQL> commit;
Commit complete.
SQL> quit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
[oracle@ozawa bin]$
[oracle@ozawa bin]$ exp joelp/joelp file=joel.dmp log=joel.log
Export: Release 9.2.0.1.0 - Production on Thu Mar 4 09:47:40 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user JOELP
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user JOELP
About to export JOELP's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export JOELP's tables via Conventional Path ...
. . exporting table T1 1 rows exported
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully without warnings.
[oracle@ozawa bin]$
[oracle@ozawa bin]$ sqlplus joelp/joelp
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Mar 4 09:48:41 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> drop table t1;
Table dropped.
SQL> quit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
[oracle@ozawa bin]$
[oracle@ozawa bin]$ imp joelp/joelp file=joel.dmp
Import: Release 9.2.0.1.0 - Production on Thu Mar 4 09:49:16 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export file created by EXPORT:V09.02.00 via conventional path
import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
. importing JOELP's objects into JOELP
. . importing table "T1" 1 rows imported
Import terminated successfully without warnings.
[oracle@ozawa bin]$
[oracle@ozawa bin]$ sqlplus joelp/joelp
SQL*Plus: Release 9.2.0.1.0 - Production on Thu Mar 4 09:49:28 2004
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
SQL> select * from t1;
C1
10
SQL> quit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
[oracle@ozawa bin]$
[oracle@ozawa bin]$
Joel Pérez
http://otn.oracle.com/experts

Export Logical Schema

How can we export logical schema.

Hi,even i want to do the same thing(export & import Data Server without losing Logical Schema connectivity).Please let me know if it is possible and how can it be done?

Create MDM repository from repository schema.

Hi,
I have exported MDM repository from one MDM console schema and saved it. Now I am trying to create a Repository from a different MDM console using this Schema. I am getting the Error "ERROR LOADING FILE".
The versions of these MDM are different. Is this causing the failure? How can I overcome it?
regards,
MRao

Hi Mahesh,
This is an Un-usual error, which even I am facing. In my case there is no version mis-match. I am trying to take the Export the Schema from a rep in 1 MDM server and then importing into another rep in another server.
Hence it might not be a version issue.
However, check the following things in your case.
1. Check the Original repository for error and repair them if found any. Upload your repository with Updated indices. Export the schema out and save it on your desktop.
2. Try creating a new repository using Import Schema on the same MDM server and check if its still showing you an error.
3. Try importing the schema on an Existing repository on the same MDM server.
4. Try Importing the schema and create a new repository on a different MDMserver.
Please check it in a test environment and no need to press the OK button while Import schema. We just need to see if the Import schema windows opens.
If in any case, you do not find the error, then probably we can understand the clear reason of the Error.
If error still persists, then would advice you to raise an SAP ticket for the same.
Hope this info helps.
Thanks and Regards
Nitin jain

Exporting XML schema

Hello All,
When i am trying to export xml schema of repository in console it is giving Unhandeld exception.
Can any one have any idea about it?
Thanks
Ankit

Hi Ankit,
Exception in Exporting XMl schema can occur due to the following reasons
1) If there are any Fatal error that cannot be repaired by MDM.
Check to see if there are any Fatal errors which cannot be repaired and see the log.If there is some field or lookup table error which you cannot fix then try deleting and recreating it and then recheck the rep.
2)The second possibilities could be the format is not saved as XML while exporting.Check it.
Hope it helps
Thanks & Regards
Simona
Edited by: Simona Pinto on Feb 27, 2008 10:50 PM

MDM 7.1.4 SP4 don't Export Repository Schema

Similar Messages

Maybe you are looking for