MDM Patch

Hi Guru's,
We are using MDM on stand alone server. we have a full landscape including back-end connectivity with SRM. I have to apply the patch to it. currently we are on sp05. I hve to update it to sp06. I have downloaded new patch last week. I'm very confused. Can someone please provide me some steps how to go through. I really appreicate your help.
Thanks,

Hello,
Before upgrading the complete MDM System, you need to stop all components of your MDM system on this host. The necessary activities are:
1. Make sure that no users are actively logged on (Data Manager, Import Manager, Syndicator, Publisher, Image Manager and all components accessing MDM via COM API or JAVA API or Portal)
2. Use MDM Console to unload all active repositories
3. Verify and repair repositories and ensure there are no errors
4. Stop all servers based on the current host (MDM Server, MDM Layout Server, ImportServer, Syndication Server).In Windows Services, check if all servers like MDM Server, MDM ImportServer, Syndication Server or Layout Server are stopped.
5. All applications running on the current host are stopped (e.g. Web applications calling the MDM host directly have to be stopped, while Web applications relying on a slave can continue)
6. Take the archive of all your repository (.a2a files) and save them apart from the MDM Server installation directory.
7. Then unistall the current MDM Server's and all GUI Clients then again install the latest MDM Server's and all the MDM clients which you want to upgarde.
8. When you installled all the components then move all the Archieves (a2a files) into the Archieves folder and then unarchieve and load them with update indices.
9. After that just update the each and every repository (with update repository option) which you have unarchieve on the updated MDM Server.
you can also refer the mentioned below threads for MDM Server upgrade:
Re: upgrade mdm5.5 sp04 to sp06
Hope this will solve your problem.
If you are using the SRM-MDM Catalog then go to the following steps:
1. Undeploy all the SCAs by using SDM.
2. deploy the SCAs of latest patch you have installed and restart the portal server.
3. Do the necessary settings to configure the SRM catalog.
TNR,
Saurabh...
Reward if found helpful.
Edited by: Saurabh Kumar Sahu on Jun 20, 2008 4:48 PM

Similar Messages

MDM Patch update

Hi Support,
As per the SAP recommendation we need to upgrade the support packages for MDM 5.5 SP6 5.5.64.75 to 5.5.65.91with DB oracle 10.2.0.2. We are using the Master/Slave methodology for catalogue management. We are using MDM data manager for catalog management, MDM Import Manager to load file data and MDM Console to check and synchronyze the SLAVES .
We have downloaded the patches from the below path --> Support Packages and Patches - Entry by Application Group -> SAP
Application Components -> SRM Catalog -> SRM-MDM CATALOG 2.0
Here we have downloaded two files:
SRM-MDM Catalog 2.0 SP04 Patch16 OS-Independent basis +
SRM-MDM Catalog 2.0 SP04 Patch16 for (HPUX...?)
When we unzip the files we have -->
MDM GUI CLIENTS , HPIA_64 , SRM-MDM_Catalog_UI, BP MDM TECHNOLOGY, BP MDM APPLICATION, MDM JAVA API
MDM WEB UI , MDM CLIX, Business_Content, BP SRM-MDM.
These files contains .sca , .a2a ,.bin files as well as .exe files , plese guide us that .sca files need to be deployed on MDM instance or SRM instance. Do we need to apply all the files or we can work with applying selected patch files.
Please share some documentation for applying the patches to MDM server. It would be of great help.
Warm Regards
Chirag Kohli

Hi ,
I am confused.
In the first line you mentioned that you have to update MDM patch but you are downloading SRM MDM calaog 2.0 patch.
First make sure which patch you have to update.
If you have to update catalog patch then it is ok otherwise you are updating wrong patch.
If you have to update mdm 5.5 patch then follow this path
Download -> Support Packages and Patches -> Entry By Application Group -> SAP NetWeaver -> SAP MDM -> SAP MDM 5.5
Thanks,
Sudhanshu

Repository connect issue after MDM Patch Upgrade

MDM Expert
We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
SAP is asking to create new DB Instance for MDM.
If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
Please help
Thanks
Deelip

Solution provided by sAP

MDM Patch Upgrade

Hello Experts,
I am facing an issue during the Upgrade of MDM on QA Server from MDM 7.1 SP05 Patch 1 to patch 34.
Below is the process that i am following for the upgrade, please correct me if I am wrong.
1. Stop the server
2. Run the SAP INST which will take you to a step by step process from root/<sid>adm users.
3. Select the option Update.
4. At one point of time it should ask to choose the new TAR file (for Patch 34) for MDM Server, MDM IIS and MDM SS. You can refer to those files here and proceed.
5. Finish Upgrade.
The issue is that, I am not asked for step 4. Please let me know if I am suppose to unpack the .TAR files or use a separate Installation Master for the Upgrade.
Regards,
Renu

Hello Renu
If you miss step 4 i think you update from your previous installation
I think, version number should be exchange.
Could you check version number your mds mdis and mdss and compare with perevious one?
Regards
Kanstantsin Chernichenka

MDM installation on AIX 5.3 core dumps

Hi all,
We installed MDM 5.5 SP4 on AIX 5.3 ML 5 (and the latest patches were applied last week-end).
The MDM Server, Import and Syndication daemons are started.
Database is Oracle 10.2 (corresponding Oracle client is used), installed on the same server.
MDM client software is in sync with the server level.
Since the installation, we get core dumps of the mds daemon (even when trying to perform the most basic operations). Consider it to be completely unusable for testing anything. You look at it, it breaks. Sorry, but that is how it is.
MDM Patches and hotfixes to the patches have been applied up to the latest level The problem is reported at SAP Support and they have core dumps, logfiles, trace files for studying. So far, the only feedback we got was to install MDM on its own server (it is a trial installation on a server where other applications are running - though I can hardly see that as a cause for core dumps).
My questions :
- are we unique in running MDM on this software paltform ?
- are others (if they exist experiencing the same problems on AIX 5.3 ?
To be honest : for the moment we are thinking about reinstalling on a Windows server.
Thanks in advance for any feedback,
Frank Van Overloop

Hello,
we have finally made some progress on this issue.
Basically, we suffered from a combination of :
- wrong usage of the product
- probably shaky exception handling in the AIX version
The cause was found by SAP MDM support after we reconstructed the problem while using a special debug-version of the mds executable. This produced a usable dump.
--- extract from the SAP reply -
The core dump shows a crash in recalculating the family tree after the
import. Family tree is being used only to create printed catalogs (which require the publisher and an additional license).
1) Do you have any value in the categories table?
2) Does the MDM server crash if you cancel the automatic family tree
recalculation in the import map, and answer "no" in the dialog box which asks to recalculate the family tree?
3) Do you intend to create a printed catalog?
If the answer to any of the questions is "no", then this asserts that
the recalculation of the family tree should not take place at all. In
this case the family table could/should be deleted. And this should not
reoccur.
end extract -
After we deleted this family table, the tests are running stable.
It's a pity that the program does not 'die' in a more elegant way or gives some understandable indication on what is going wrong.
It also looks like this exception is handled better on the Windows implementation. The same 'functional mistake' was made there and this produced no dumps at all. Could be a porting issue from one platform to another.
Regards,
Frank

MDM Server on Linux, Console on Windows - status is "stopped"

We installed MDM (SRM-MDM) on a Linux systems with MaxDB. The server itself seems to run fine:
Starting: - Thu Dec 4 12:47:52 CET 2008
Linux mdmtest 2.6.16.60-0.33-xen #1 SMP Fri Oct 31 14:24:07 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
file size               (blocks, -f) unlimited
pending signals                 (-i) 128064
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 128064
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/xvda1            57677500   4284708 50462940   8% /
udev                  27262976       144 27262832   1% /dev
-rwxr-xr-x 1 root root 48603243 2008-12-03 16:19 /opt/MDM/bin/mds-r
mds Version 5.5.63.77
        Built on 2008-Oct-20
Client Interface Version 5.5.63.02
        - Interface CRC=0xf39a67cb
Console Interface Version 5.5.63.02
        - Interface CRC=0xf1cd6216
Web Interface Version 5.5.63.00
        - Interface CRC=0x9d7cb0c4
Program is now exiting ...
Loading shared library: ncs.so ...
ncs.so loaded.
When we try to connect an MDM Console from a Windows box it´s always showing the server as "stopped" although all the services are running:
mdm@mdmtest:~/mdm/mds> ps -ef | grep mds-r
mdm      12653 12652 0 12:47 pts/0    00:00:16 /opt/MDM/bin/mds-r
mdm      12896 12855 0 13:19 pts/0    00:00:00 grep mds-r
We already tried different versions of the console but it always is just "stopped". I can ping and telnet from the machine running the console, I can connect to the MDM ports (20003, 20004 etc.) without any problem.
That version numbering with SRM-MDM, patches, service packs and hotfixes and the actual build numbers is very confusing. I have no clue what else to try, maybe someone has an idea before I need to open an OSS call..
Thanx!
Markus

Hi Christian,
- When mounting the server in Console rather enter the IP of the server than its name.
I put the name in the hosts file of the Windows machine, I tried both - always the same
- Try to connect via CLIX ("clix mdsstatus" command). This should come with your installation.
C:ProgrammeSAP MDM 5.5CLIX>clix mdsStart <internal-ip>:MDT
Error: 0xffffffff, Unspecified error
- Can you actually start the server if it is stopped?
No - MDM-Console tells me, that it can´t connect to the Windows service...
Otherwise, I'm clueless at this moment as well. Keep us updated.
I will - thank you!
Markus

Change the field details in MDM Console

Hi All
I have unloaded repository and try to change the fields details ,like changing the display fields option as yes or no. in MDM Console .
But it is not allowing me to do so and giving error message as "field name already exists"
But when I go and change the user defined field it allows me to do so.
Same is the case with Table details
Can you guide me on this.
Thanks
Suds

Hi Suds,
If you are using the same and the latest MDM patch for both your original and the Test repository, it should behave in same way.
But you mentioned that for test repository, you are not facing any problem.
Try out these steps to debug your original repository:
1. Check your original repository for any errors and also if found any, then repair it.
2. Also try to archive your original repository and then unarchive it with a different name. ( And check whether it is still behaving the same).
3. You can also try creating a duplicate repository and test it.
4. Unload and Re-load (with updated Indices) your original rep and test it.
I hope any of the above steps helps.
*Please reward points if found useful.
Thanks and Regards
Nitin jain

MDM 5.5.65.71(Not able to load the repository)

Hi All,
We are getting the strange problem in MDM patch 5.5.65.71.
We have recently upgraded to 5.5.65.71 from 5.5.64.79 and we are getting problem one of our repository while we try to load it.
The repository is not getting loaded saying that unique constraint violated and duplicates are there for one of the field.
We have removed the unique constraint in the console level and loaded the repository to check whether any duplicates existing or not. But no duplicates existing in that repository.
We have again kept unique constraint in the console level and tried to load the repository but we were not able to do it as it is
saying unique constraint violation eventhough there were no records which violates unique constraint on our repository.
Has anyone faced this problem?
Please share your views on how to get rid of this issue?
Thanks,
Narendra

Hi,
I would suggest, if you have backup archive file of the repository, then please try by deleting and again archiving repository. it may solve problem. It is suggested to check and verify and take backup of the repository before upgrading MDM server.
please revert if you don't have backup of the repository.
Regards,
Shiv

MDM 5.5 SP06 Support on SRM 7.0

Hi
We are using SRM 3.0 (EBP 4.0) with requisite catalog to maintain the catalog
We are going to upgrade SRM to SRM 7.0 and would like to use our existing MDM 5.5 SP06 lanscape (It is being currently used to maintain our company Product Master)
Can someone tell me that the latest SRM version 7.0 can use existing MDM Landscape without any issue
We have very small size of Catalog which we are using with SRM 3.0
Thanks in advance
Thanks
Deelip

Hey Deepali,
I informed you about best practice and SAP's recommendations.
My thoughts on WHY SAP RECOMMENDS SEPARATE LANDSCAPE FOR SRM-MDM CATALOG are as follows:
1. Version strategy of SRM-MDM Catalog is different from MDM Product version strategy. And from my experience what i have seen, compatible package of SRM-MDM Catalog is released with in 1-2 month of release of normal MDM. You may face a situation that a new version of MDM is available but SRM-MDM Catalog version compatible to this MDM version is not released..
For example, As of now, MDM 7.1 SP05 is the latest version, but latest version SRM-MDM Catalog version is based on MDM 7.1 SP04 and as of now MDM 7.1 SP05 is not yet supported for SRM MDM Catalog.
2. if You face any compatibility problem or issue in SRM-MDM Catalog and have to upgrade MDM patch to fix it, then it will disturb your other master data object processes too.
3. SRM-MDM Catalog UI should be compatible to MDM Server Version and is based on a specific MDM Release. You may face a situation that SRM-MDM Catalog package not exactly matching your MDM Server version.
Please check the version mapping note for SRM-MDM Catalog 2.0 and MDM 5.5. this will explain this point in a better way..
SAP Note 1083126 - Version mapping SRM-MDM Catalog 2.0 to SAP MDM 5.5
But, on the other side, i don't see any technical restriction in using SRM-MDM Catalog with other Master data objects (* if you can get SRM-MDM Catalog package matching to your MDM server version)
So, you can also use same MDM server in above case.
Hope this will clearify things more...Revert if any further question...
Best Regards,
Shiv

Change Tracker does not automatically log in

Good day,
Could you please assist. We have just successfully upgraded our MDM patch. The problem is that when a user is logged in to Data Manager, previously they could automatically be logged into the Change Tracker tab at the bottom. Now, it prompts the user for their logins before allowing them access. Is there any way we can automatically provide access again?
Thank you.
Regards,
Simni

Hi Simni,
As you have posted this question into Portal Implementation forum, I assume that you are using MDM Change Tracker application in Portal. However, if you are getting issue with the change tracker tab in Data Manager, you should post your question into MDM Forum.
Coming back to your question, after patch upgrade, have you made it sure that Change Tracker Data Source is working normally as it was previously? Do check that both MDM Destinations and Data Source are working fine.
Ameya

SRM-MDM 3.0 SP10 Patch 1 - logon failed

Hello there,
we have a urgend problem after upgrading the SRM-MDM Components and the MDM Server.
Problem is, that we are not able to logon to the app ui or the search ui. It's not a Problem with the user. When logon to the app ui we receive the message "logon failed".
Connection to the Repository via MDM Clients works very well. Only the Web UI is not accessable.
To be sure we are having the right SPs for the Components we downloaded the latest Support Stack that includes all components versions that fits to each other (thats what i think).
At least we have now
MDM Server SP06
MDM Catalog SP10 Patch 1
Java API SP10 Patch 0
MDM Connector SP10 Patch 7 (?)
Here's the information from the connection test via mdm utilities
!======================================!
Host-Adresse = 10.199.29.243
Host Name = mpgmdms
Repository-Port = 2000
!======================================!
MDM-Server-Ports werden geprüft...
Verbindung ok (Port 59950, Zeit = 0 ms)
Repository-Ports werden geprüft...
Verbindung ok (Port 2000, Zeit = 0 ms)
Verbindung ok (Port 2001, Zeit = 0 ms)
Verbindung ok (Port 2002, Zeit = 0 ms)
JAVA-API-Version von MDM ermitteln
Admin Version = 7.1.07.101
Build Version = 7.1.07.166
Content Version = 7.1.07.101
Meta Version = 7.1.07.101
!======================================!
Verbindung zu MDM-Server 10.199.29.243 wird hergestellt
MDM-Server-Version wird ermittelt...
Version = Version 7.1 (7.1.06.234 Win64)
!======================================!
Installierte Repositories werden ermittelt...
-> MPG_DEV_MASTER (S36/ORCL)
-> MPG_DEV_SLAVE2 (S36/ORCL)
-> MPG_DEV_SLAVE (S36/ORCL)
-> MPG_TEST_REPOSITORY (S36/ORCL)
From the visua administrator we get the following releaseinformation:
MDM_Connector 1000.710.700.7.1.201105150802
MDM_JAVA_API 1000.710.0.7.166.20110410110411
SRM_MDM_CAT 1000.3.0.10.1.20110429065011
Within the MDM Console we get a some log entries when trying to log in.
Hope you can help me.
Thank your
Rico
Edited by: Rico Stoll on May 25, 2011 6:31 PM

ur API / connector and MDS are on diff SP levels :
JAVA-API-Version von MDM ermitteln
Admin Version = 7.1.07.101 Interface CRC=0x7d50b0cf
Build Version = 7.1.07.166
Content Version = 7.1.07.101 Interface CRC=???
Meta Version \t= 7.1.07.101 Interface CRC=0x3a0a3732
!======================================!
Verbindung zu MDM-Server 10.199.29.243 wird hergestellt
MDM-Server-Version wird ermittelt...
Version = Version 7.1 (7.1.06.234 Win64)
upgrade the MDS to SP 07 and things should start working !
thanks
-Adrivit

History and Next Step not working in UWL SAP MDM 5.5 SP6 Patch 2

Hi,
Im not able to send a record to other process step with other roles in a WF.
When USER 1 logs on its possible to send the record to the next process step where USER 2 is assigned. When USER 2 logs on, the user is not able to send it anywhere, the iView is empty.
Its the same problem when we press the history button. In the first step of the WF its possible to see history. In the second step the history iView is empty.
Any ideas?
BR
Michael

I've seen issues like this as well. There are a variety of issues that came out of the SP06 Patch 2 upgrade which effect the MDM workflow and Portal UWL. I would recommend checking out the latest hotfix as I think it resolves a lot of these problems. The latest build is 5.5.62.50 (5.5 SP06 Patch 2 Hotfix 4). They released four hotfixes within a month (I think) so my guess is they are aware of the issues with SP06.

Can not download MDM 5.5 SP05 Application Patch 1 (Build 5.5.41.58)

I was able to download all other components of MDM SP5 Patch 1, except
MDM 5.5 SP05 Application Patch 1 (Build 5.5.41.58) (BPMDMA55005P_1-20001090.ZIP). It doesn't show up in download manager.
Anybody else had luck downloading this file?
Is it a bug or access issue?
Thanks,
Abhay

No error message.
Component doesn't show up in Download basket. So can not download it.
Earlier it was nice, just right click on the link you could save the Zip file.
Abhay

In Portal MDM system missing

Hi,
Iam using the discovery system for creating a POC i was going through a SDN demo on MDM portal where they have show me to create a MDM folder and assign it to the MDM system templete. Here Iam not getting this <b>MDM SYSTEM</b> Can any one help me in this please.
Iam struck here in Potal part of MDM.
Thanks,
Suresh

Hi Sridhar,
Go to SAP Service Market place http://service.sap.com
Select
Software Downloads>>Entry by Application Group>>Support Packages and Patches>> SAP NetWeaver>> SAP MDM>> SAP MDM 5.5>>Portal Content
download the following 2 files.
1. BP MDM APPLICATION 5.5
2. BP MDM TECHNOLOGY 5.5
The above 2 files are available via SAP Solution Manager.
Thanks
Subbu

SRM-MDM Catalog Installation/Landscape

Hi,
We are currently having the following landscape in place with regards to the SRM, MDM and SRM-MDM Catalog :
Server 1 : SRM 5.0 Running   (HP-UX)
Server 2:   Enterprise Portal running with MDM Content and SRM-MDM Catalog JAVA components (HP-UX)
Server 3:   Standard MDM Server installation (Windows 2K)
We have configured everything according to the notes and guides (including the guide from Sudhendu Pandey), but when we try to configure the Search UI in Webdynrpo, the java components cannot connect to the MDM host and we are getting just the connection failed error.
My questions are :
1)   Can we run with the above landscape or is it necessary to have the SRM-MDM Catalog Java components installed on the same server as MDM.
2)   Do we have problems with versioning of the MDM server and the SRM-MDM java components ? We already replaced the MDM_JAVA_API with the correct one, but I do not have a newer version of the other api.
3)   Do I need to configure anything on the MDM server to get this running ?
Thanks in advance for your help
Regards
Raymond

Hi Foh,
Apologies for my late reply, but I was travelling. Thanks for this tip. We were using the latest versions for the MDM Portal Content, but the API for the SRM-MDM catalog was different.
I have updated this API with the latest version (Patch 3 HF 1) and now I can logon to the MDM server and I see the MDM Repositories. However if I now try to logon to one of the repositories he gives me the same error that the Login has Failed. The user that I am using is the default one coming with the SRM-MDM repository (Admin).
Regards
Raymond

MDM Patch

Similar Messages

Maybe you are looking for