Solman upgrade

Hi All,
We are planning to upgrade Solman to 4.0. I have couple of doubts regarding the upgrade
1) existing solution manager is non-unicode , is it mandatory that we need to migrate to unicode to have solution manager 4.0
2)it would be great if anyone can send me the upgrade document ( not the SAP upgrade) that you prepared
Thanks
Jini
PS: All imputs will be awarded

Hi Jini,
1) It's not mandatory to use SAP Solution Manager 4.0 on unicode.
Information about the availability for upgrades can be found in the Product Availability Matrix of SAP Solution Manager 4.0:
http://www.service.sap.com/~form/handler?_APP=00200682500000001303&_EVENT=DISP_NEW&00200682500000002804=01200314690900000235
Best regards,
Ruediger Stoecker

Similar Messages

  • Solman upgrade 7.1 error in  PREPARE_JSPM_QUEUE

    Hi All,
    We are upgrading solman from 7.0 EHP1 to 7.1 , getting the below error in  PREPARE_JSPM_QUEUE phase
    " Checking whether product SAP SOLUTION MANAGER with version 7.1 is supported by this EHP Installer.
    Feb 21, 2012 6:04:32 PM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.validateProducts(JSPMSpStackQueuePreparator.java:309) [Thread[main,5,main]]: The product is not supported.
    Feb 21, 2012 6:04:32 PM [Error]:                       com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase."
    I had checked the note Note 1431340 - EHPI fails at PREPARE_JSPM_QUEUE phase - stack rejected, no solution got .
    Can anyone advice please
    Regards,
    Nibu Antony

    Hi
    @ Nirmal
    For solman upgrade tool is Solmanup nad version is as below:
    Client Version 1.5.0 Server Version 1.5.0 Server Port 4241 DSUService
    Version: 1.1.6  Configured Plugins 
    Plugin ABAP at Version:      
    1.0.3      
    Plugin J2EE at Version:      
    1.0.5      
    I had already gone through the thread and the note as mentioned in initially, no luck still..

  • Solman Upgrade: impacts on TAO 2.0

    Hi Expert,
    I'm planing to upgrade solution manager from 7.0 to 7.1 sp11. Currently I have SAP TAO 2.0 SP7 (ST-TAO 200) and HP QC adapter version 1.0 (ST-QCA 100)  installed in my SAP SM 7.0. I would know if I will have any impact on these 2 components after the upgrade. In particular I sow that in SM 7.1 the new SAP TAO version has been included in the SAP TST addon. My question is, can I still use the add-ons ST-TAO 200 and ST-QCA 100 in my SM 7.1 SP 11?
    Thanks in advance for the support.
    BR
    gio'

    Hello Gio'
    As Divyanshu pointed, ST-TAO 2.0 is compatible with 7.1
    Also  ST-QCA 100 doesn't change.
    I first personally upgraded from 7.01 SP25  to 7.1 SP07 last year and decided to do the TAO upgrade from 2.0.4 to 3.0 SP02 a few weeks after the solman upgrade as the solman upgrade is quite an exercise on its own.
    Just one note in regards to the QC adapter, if you're on solman 7.0, after the upgrade to 7,1, you will have to update the message ID protocol with the option “Suppress ID transfer".
    Also in regards to QC, I was just using the requirements and test results transfers [I wasn't using defect management integration so I cant tell you if extra work would be required for this 2nd area of the QC integration]
    Cheers
    Francois

  • Issue after solman Upgrade

    Dears,
    We were using solman 7.0, connected to ECC 5.0 server.
    We configured all activities EWA,System Monitoring and all were working fine.
    Now we upgraded solman to 7.01(EHP1) and R/3 to ECC 6.04 .
    1 - My first concern is after upgradation it should automatically pick details but is is still showing ECC5 in product version.
         We performed Read data from remote system also but still same issue.
    2 - When I go to EWA or system Monitoring I only find Prd server there while in solution's logical component all dev,qas and prd servers are available.Earlier before upgrading it was showing all systems in EWA and system Monitoring.
    Please suggest.
    Shivam

    Hello Shivam
    For point #2 please look closely at the solution containing the systsem and make sure that 1) The Dev, QAS systems are included, and are highlighted greeen ( Meaning they are status "Put in Solution"). It sounds a lot like this setting is not done, therefore the systems would not show when you would try and use that solution in functions like EWA, BPMON, etc.
    It sounds very much like when you create a new soltuion with PRD, QAS, DEV systems assigned, but only the PRD system is "Put in Solution" by default, so you explicitly need to right click the system in change/edit mode, and select "Put in Solution", then save.
    Now why this might be the case after the upgrade, I don't have an answer, but it is worth having a check as the symptom fits this issue. I would advise you check the solution itself and ensure the DEV and QAS systems and in status "Put in Solution".
    Hope this information is helpful.
    Regards,,
    Paul

  • Export DVD for product CRM/SOLMAN Upgrade Solution Manager 7.1

    Hello Experts,
    It is my first time doing an upgrade and I have a problem, the SOLMANUP tool gives me: "Enter at least the mount point containing "Export DVD for product CRM/SOLMAN"", I downloaded from SMP the 12 parts of the SAP Solution M. 7.1 Upgr.Export (51039400), I got now 1 .exe file and 11 .RAR files and when I put the path, the SOLMANUP doesnt recognize as a valid mount point, any advices?
    Regards,
    Paul

    Hi Paul,
    Have you already checked note 1577909?
    Note: 1462137 - Add. info. about Upgrading to SAP Solution Manager 7.1
    Please enter mount points for the DVDs required for the upgrade.
    Enter at least the mount point containing "Export DVD for product
    CRM/SOLMAN"
    Please check if the requested Data Carrier is mounted on any of the mount points:
           Path                                     Description
          +                                        +             +
         1 /usr/sap/SMP/SOLMANUP/51042010
         2 /usr/sap/SMP/SOLMANUP/51040039
         3 /usr/sap/SMP/SOLMANUP/51040119
         4 /usr/sap/SMP/SOLMANUP/51040868_2/DVD_OS_
         5 /usr/sap/SMP/SOLMANUP/upgrade_export_dvd
         6 /usr/sap/SMP/SOLMANUP/upgrade_export_dvd
    You will have to download all the archives and then extract them. Please go through the
    SAP Note 886535 for these kind of archives. Once everything is archived
    and extracted, provide the path.
    Thanks
    Regards
    Vikram

  • Solman Upgrade Steps

    Hi All,
               Can any one explain me the steps involve in Upgrading a Support Package in SOLMAN?. I request you to send me a steps as soon as possible. At the same time, i want  to know how to use maintainence Optimizer?

    Hello,
    all is explained in detail in the Solutionmanager documentation:
    service.sap.com/solutionmanager - SAP Solution Manager in Detail - Maintenance Optimizer
    It is important that your landscape is maintained properly.
    The Maintenance Optimizer can be accessed via transaction dsmop - select your solution - goto tab Change Management - choose Maintenance Optimizer - create a new maintenance task
    or via the workcenter
    Use transaction solman_workcenter - chosse tab Change Management - choose Maintenance Optimizer on the left - create a new maintenance task
    Christian

  • SAP Solman Upgrade from 7.0 to EHP1

    Hi Experts,
    We want to have upgrade for our solution manager from 7.0 to EHP1.
    Need your quick help to fix the plan of action.
    Regards,
    Abhinav

    Hi,
    There is nothing available read made.
    Yes,  i hope 2 days time is more than enough, more over its depends upon your system environment.
    We advice you to use Mopz for downloading all packages to avoid any discrepancy later.
    You might want to look into SAP Note
    Note 1169247 - Additional info for Solution Manager 7.0 EHP1 update[ Note 1169247 - Additional info for Solution Manager 7.0 EHP1 update|https://service.sap.com/sap/support/notes/1169247]
    All the best.
    Regards,
    Gagan Deep Kaushal

  • Solman upgrade to EHP1 fails in ADDON_CONFLICTS_? step

    Hello,
    I am trying to install EHP1 for Solution Manager 7.0. These are the steps I followed:
    1.Updated Java stack to SPS17 using JSPM.
    2.Updated Java stack to EHP1 using JSPM.
    3. Updated SPAM/SAINT patch level to 35.
    4. Updated Kernel to 7.01 patch level 23 using JSPM.
    After this, I tried to import EHP1 using SAINT for the ABAP stack. It fails in the phase ADDON_CONFLICTS_?
    SAINT gives me the following message:
    "There are conflicts between different Add-Ons or between Add-Ons and Support Packages...."
    Below the message it lists the CRTs (Conflict Resolution Transports) in a table.
    SAPK-701DHINSAPBASIS -> Include CRT SAPKITL428
    SAPKB70101 -> Include CRT SAPKITL428
    SAPKB70102 -> Include CRT SAPKITL428
    SAPKB70103 -> Include CRT SAPKITL429
    I have included these CRTs in the queue, and tried to reimport. Got same message again. I applied SAP note 124101. But I am still not able to get past this phase.
    Any help in this regard would be highly appreciated.
    Thanks,
    Ajay

    Hello:
    That error is resolved when you put in the same queue all the components. Look the note: 1169247
    Javier.-
    Edited by: Javier Caballero on Jun 14, 2009 5:23 AM

  • EHP 7 upgrade & Mopz in Solman 7.1 SP 8

    Hi Everyone,
    I am currently working on EHP 7 upgrade for my ECC 6 EHP 6 system. I began my work in ECC with SLD data push and SMSY, LMDB config, in Solman now moved on with MOPZ config to download EHP SPS. I have a query here, is it important to have the entire system data updated with SMSY and LMDB in Solman? i understand that MOPZ checks the current system Patch level from SMSY/LMDB and based on our target selection it calculates and recommends. just wondering how exactly it happens!. Bacause we have our BO system and few other non SAP systems in the landscape that are not updated with the SMSY/LMDB but they also should be considerd for the upgrade to check if there are dependencies.
    so my question is, do we have to push data from non sap also and maintaine in SMSY and LMDB before we perform EHP SPS download from MOPZ?
    other question is, if we perform upgrade in a ECC Sandbox environment (usually a copy of Production), it is not necessary to have sandbox for Portal, PI and other systems. so what is the recommended approach here? do we have to select the Developement  ECC system from MOPZ so that we will have other Dev systems (PI, Portal.,..etc) present in the SMSY & LMDB and MOPZ recommendation will be perfect?
    please help me understand this
    Thanks,
    Shiv

    Instead of reviewing SMSY, you should switch over to the LMDB as it is the future for system data in SolMan.
    The reason its telling you ERP 6.0 SPS25 is because it is not taking into account your Ehp, SAP still has to support customers who haven't taken the Ehp (perhaps unicode issues, 32 bit to 64 bit, etc) so this is a way to compare.  I found a bar graph that explained this in a very simple picture, however I can't find it online and leads me to believe I read/saw it in a book.  Also think of this my company is currently updating ECC from Ehp 5 SPS 4 to Ehp7 SPS 4, the SPS are the same due to the Ehp change and resetting the SPS counter back to 0, but in mopz I believe it shows SPS 28 or 29 for ECC 6.0; so essentially there is nothing you can or need to fix for the system data.  If this is still confusing I will try to track down the bar graph example I saw.
    As for logical components you can create your own (and is advised to do so as SAP could remove entries on you during a SolMan upgrade) so you could list it as z_ERP or zEhpERP or z_ECC; however it makes sens to you and your co-workers/customer, when you manage the system and the button that allows you to configure the system, the first section in the new window stays red until you assign a logical component to the system.  So you might already have something assigned to the system(s).
    SAP doesn't list it as BO, and I'm not sure if you can run a successful mopz on BO systems; if you leverage the PAM at SAP you can track down dependencies.  I also believe Process Orchestration is only 7.3/7.31/7.4 which is compatible with Ehp 7.
    SAP PAM:  http://service.sap.com/pam
    As for BO, do you have the following under the SWDC?
    Installations and Upgrades - B" SBOP BI platform (former SBOP Enterprise)" SBOP BI PLATFORM (ENTERPRISE)" SBOP BI PLATFORM 4.1

  • Solman 7.1; delete old database from SMSY

    We have done upgrade to solman 7.1 . So we use SMSY with datasource LMDB now.
    In former times the database host of some SAP-systems  were changed.
    So we have some old obsolete entries like database <SID>_0001 in SMSY (sent by SLD BEFORE the solman upgrade.
    If we try to delete old entry in SMSY-> databases by right mouse click , system opens the LMDB maintenance, because maintenance should normally done in LMDB.  There is no database <SID>_0001 in LMDB and the SLDs  - only the correct  System <SID> with database <SID> with correct server data.
    How can we properly delete the obsolete entries in SMSY ?
    In the LM Db Setup Guide I only found some troubleshooting for sync problems between LMDB and SLD, but not how to delete manually in SMSY in SM 7.1. Any ideas ?

    I have solved the problem.
    The obsolete database was only in SMSY and NOT in SLD + LMDB - so no deletion possible in SMSY and LMDB (as suggested by community)
    The obsolete database <SID>_0001 was not used by any SAP system in SMSY.
    I used the workaround of creating a dummy database system with the obsolete name in LMDB for later deletion  and sync to SMSY.
    steps:
    I create a new technical system  in LMDB: select type " Database system" instead of default "ABAP ....."
    Identification of technical system:
    databasename: <SID>_0001
    databasehost:  you can use the correct server if you like
    databasetype: DB2, oracle, etc...
    Next screen (identification technical system):
    extended systemname: SID>_0001 (change it to the value you want to delete in SMSY.  My solman suggested <SID>00001)
    Save
    Optional: In next screen you can adapt the description of the system, which will be displayed in SMSY very quickly!
    Then delete system from LMDB => deletion of database will be synchonized into SMSY.
    Work done.

  • CHARM reconfiguration after upgrade to 7.1 SP11

    Hello,
    I have just completed the Solman upgrade from 7.01 to 7.1 SP11 successfully.
    I have also completed the
    1. System Preparation
    2. Basic Configuration
    3. Managed System configuration for the managed system.
    I have checked our CUA is also working fire after the upgrade.
    As I read the guides I see, there are changes tobe done for CHARM.
    I completed automatic steps from Solman_setup --> Change Request Management.
    One manual step is to Copy Transaction Types from OLD to NEW.
    For which Transaction Type I have to do this with the "ai_crm_cpy_proctype"?
      SMIN: Incident
      SMIS: Incident (ISV)
      SMIV: Incident (VAR)
      SMIT: Incident Template
      SMPR: Problem
      SMPT: Problem Template
      SMRQ: Service Request
      SMRT: Service Request Template
    For all the Above? or its not required ? Done automatically?
    I am doing it for the First time, Please guide.
    I am following the Standard guides, but this is not clear to me.
    Regards,
    Jigar

    Hi Jigar,
    Please go thru the link.
    Impact on CHARM & Service Desk after upgrade to SOLMAN 7.1 from 7.0
    Hope it helps.
    Regards
    Sunny

  • Cannot implement/deimplement notes; upgrade running

    Hello Experts,
    We have applied the support packs in SOLMAN system using SUM tool and it was completed successfully without any issue.
    Due to some issue we have restore the backup which was taken after the completion of downtime phase i.e. Phase 5.6(Execution).
    Now the system is up and running and we are applying the SAP note using SNOTE and it is giving this message "Cannot implement/deimplement notes; upgrade running".
    Can you please suggest which steps I need to execute again which was performed by SUM tool itself to make the system productive.
    Regards,
    Shubham

    Hello Deepak,
    In my case solman upgrade was completed successfully after executing all the phases of SUM.
    Now the scenario is
    1. After two days I face some issue due to which I have to restored the backup taken during execution phase of SUM (i.e. Phase 5.6) just before post processing phase where SUM prompt to take the database backup and enable the archive logs.
    2. This DB backup is restored successfully and now Solman system is up and running.
    3. Now if I try to apply SAP note it using snote it gives message "Cannot implement/deimplement notes; upgrade running".
    But in the SUM guide SAP has not provided the steps which we need to execute if we restore that backup. I am trying to find out which steps I need to execute manually which were performed by SUM tool itself.
    Regards,
    Shubham

  • Custom message is not getting displayed after raising do_not_save

    Hi all,
    In Order_save BADI, based some conditions, we were throwing custom messages.
    FYI., code used,
    CV_OWN_MESSAGE = 'X'.
    MESSAGE 'xxxxxxxxxxxxxx' TYPE 'W' Raising do_not_save.
    After Solman upgrade from 7.0 to 7.1, system is not displaying custom message and
    system throwing message like "The document could not be saved" only after execution of above message statement.
    How can I overwrite this system message.
    Any help would be highly appreciated.
    -Mahi

    Hi,
    Please check the below notes
    1922870 - Raising DO_NOT_SAVE event from ORDER_SAVE BADI cause dump
    1650635 - Work Center: problems when using BAdI ORDER_SAVE
    Rg,
    Karthik

  • Single stack vs. Dual Stack - Why does SAP recommend single stack?

    Hello SAP,
       I am a business partner who specializes in infrastructure consulting for SAP solutions.  The SAP Consultants I am working with recently have been recommending that customers install single stack systems.  I would like to know why? Are there problems with dual stack systems?  Is SAP changing things in a later release and they want customers to be prepared for the change?
      From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers.  I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
      I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other.  This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!!  Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
    Regards,
    Zaz

       I am a business partner who specializes in infrastructure consulting for SAP solutions.  The SAP Consultants I am working with recently have been recommending that customers install single stack systems.  I would like to know why? Are there problems with dual stack systems?
    The problems are:
    - difficult to size and maintain - Java + ABAP will fight for resources (memory,CPU) and there´s not much one can do to tune if either ABAP or Java as dual stack instance on a single box is running nuts (for whatever reason).
    - System copies via R3load - if you want to copy a huge system (let´s say ERP 6.0 + Java stack) you need to use sapinst + R3load to do the copy. Imagine if the system is 1 TB or bigger, this is very time consuming
    - Upgrades are complicated - if you upgrade a dual stack system you need to run two PREPARES and two upgrades at the same time - there are sync points each upgrade wait for the other to finish --> difficult to plan in sense of runtimes and even more notes/preparation to do (a dual stack SolMan upgrade from 3.2 to 4.0 had almost 100 notes (technical!) and two upgrade preparation guides...)
    - interdependencies - example: you run ERP + EP + BI-Java on one system. You upgrade your BI (which is on a different box) to a new support package. Since the BI-Java need to be in sync with the BI ABAP support package you need to upgrade the EP too - and since there´s a direct dependency (doublestack system) you will need to install support packages on your ERP. So you finally end up in having dependency chains that a total different system (BI) will force you to upgrade/patch your ERP. And if you have e. g. a CRM connected to the same EP you will need to patch that too...
    Is SAP changing things in a later release and they want customers to be prepared for the change?
    No - the possibility of having a dual stack installation will be still there.
      From an infrastucture point of view this recommendation combined with SAP NetWeaver architecture will result in an explosion of SID names which leads to an explosion of application server instances and DBMS instances and an explosion of installed servers.  I know it is possible to combine SIDs into a single DBMS using MCOD and to have multiple application servers in a single physical server, but there are issues with mulitple application server instances and MCOD use which make normal maintenance operations difficult.
    I agree - MCOD is not a good solution for this problem.
      I think it would be much better for customers to install dual stack systems and simply adjust the SAP profile parameters to disable one stack or the other.  This way, you could still have 1 stack per application server instance and you would not be have to be creative with SAP SID names!!!  Creating a DBMS instance or installing an additional server is not a simple nor economical proposition.
    There are 36 * 36 * 36 (minus a few reserved) names for SIDs- this should be enough - also for the biggest customers
    Of course one could install both and disable the one you don´t need - but this won´t help in dependency thing. If you e. g. install a dual stack instance for CRM and disable the Java part, you can nicely run it. In case of an upgrade, you will need to upgrade the Java part too (see above) although you don´t use it. The upgrade will detect the doublestack and wait for the java instance to be upgraded too. Same is true vice versa. And believe me: you don´t want that
    In fact it is better to separate - that´s at least our experience. The main no-go for such a configuration on our side was the dependency thing. Since they are there and you can´t do much about them we decided to have a 1:1 relationship for ABAP backend and Java "frontend". You will get more instances (and names and databases) but you can patch applications independently from each other. So an implementation of a  BI patch won´t imply that you finally also patch your ERP production and other systems that connect to that portal.
    There are virtualization techniques available to not need more boxes, you can consolidate them on one machine as if you were installing a dual stack so that is not really an issue. This depends, of course, on the platform and database you use (e. g. Oracle does not support production installations in VMWare). We use for our Java instances Solaris on Opteron (or Intel 64bit) and zones/containers and for the ABAP part we use Linux + Xen. Both virtualization methods come with the OS (so no additional $$$) and both are supported by SAP.
    The propagated advantage of having a dual stack installation (shared memory access etc.) is so small that it doesn´t outban the additional complexity - which is definitely there.
    I hope those arguments will help to understand SAPs (and the consultants) position - get back if you want more
    Markus

  • The 'c' XUSER key for the DBM user does not exist or could not be identified

    Hello members,
    I am getting this message  'The 'c' XUSER key for the DBM user does not exist or could not be identified' in SUM preparation phase while upgrading SOLMAN from 7.01 to 7.1
    Does anyone has any idea on this. What steps need to be followed for this.
    My DB is MaxDB.
    Thanks,
    Srikanth

    Hello,
    Figured out the problem. Actually SAP System was moved from actual server to Virtual machine on the server. In this process some of the DB configuration got corrupted. And this activity was done by one of our previous employee.
    Since this was a standalone system, I took backup of all current configuration and uninstalled SAP and installed new Solman 7.1 SPS12. Issue is resolved now.
    Best Regards,
    Srikanth
    Solman Upgrade from 7.01 to 7.1 stuck in Extraction-PREP_EXTRACT/BEGIN_PRE phase 

Maybe you are looking for