Solution Manager upgrade to enterprise Edition

Dear All,
We are running Solution Manager 4.0 in Win2k3 32 bit server
with Oracle 10.2.0.2 Non Unicode version and ST patch level 11.
The memory of the server is recently increased from 4GB to 12GB.
We do not have any Java Stack.
We have configured EWA / System monitoring in our Solman and
also we have huge (really large) no. of documents uploaded into it.
We want to upgrade our Solman to Solution Manager Enterprise edition.
Can this upgrade from NUC to UC is possible with 32 bit OS platform
or we need to change our OS to 64 bit? If we change our OS to 64 bit,
will it have any impact on our existing application?
Also, is it possible to migrate the system as it is to a HPUX 11.31 box
without loosing any documents?
Kindly provide your views.
Thanks & Regards
Sudip

I strongly recomment to go for 64 bit in any case, 32 Bit is history...
For the migration to 64 bti you need to perform a homogenious system copy (Windows 32 Bit / Windows 64 Bit), if  your target platform is HP-UX, then you need to perform a heterogenious system copy, which is more complex. Documents will not be lost during systemcopy operations.
regards
Peter

Similar Messages

  • SSO from Solution Manager to Wily Enterprise Manager issue

    Hi,
    We are facing problem in SSO from Solution Manager to Wily Enterprise Manager. We have done the configuration as per the Wily Enterprise Guide- "Introscope Version 8 Installation Guide For SAP" Page 38.
    Our Solution Manager system is running on AIX platform and Wily Enterprise Manager is on Windows 2008.
    This is what we are trying
    SOLMAN Production Client --> SOLMAN_WORKCENTER --> INTROSCOPE WORKSTATION --> this opens a new browser page and from there we click on Start Introscope -->
    Result --> SSO doesn't work, still we get login window.
    Introscope Enterprise Manager logs says -->
    9/12/11 10:47:17 PM BST [WARN] [Manager] Single sign on failed: No SAP single sign on ticket was found in the request header.
    Note: Another Solution Manager system in our landscape (on windows 2008 platform) is connected to same Wily Enterprise Manager (windows 2008) and from this solution manager SSO to Wily Enterprise Manager is working.
    Please help me with your expertise to solve this problem.
    Best Regards
    Davinder

    Hello Singh,
    Could you check if you have maintained these parameters in instacne profile ?
    From SCN post -> http://scn.sap.com/thread/969538
    Hi Hector,
    To configure SSO as per initial setup guide, please check your profile parameters in your Solution Manager as below:
    You have set up SSO, see also:
    SAP Note 817529: Checking the SSO Configuration
    Installation Guide and Security Guide for SAP Solution Manager
    Create the following profile parameters in the instance profile:
    login/create_sso2_ticket = 2
    login/accept_sso2_ticket = 1
    icm/host_name_full = fully qualified server name
    This parameter must be attributed to the fully qualified server name (for example wdfd002568.wdf.sap). The name must contain at least two periods. See also SAP Note 434918.
    Hope this helps,
    Regards,
    -Rohan
    BR,
    kamil

  • Solution Manager Upgrade to EHP1 7.01

    Hi
    Need some help. Could you please share  upgrade doc/exp with me, we are planning for upgrade solution manager from sp17 to sp19.
    Stack level 18 or 19 is the part of  EHP1 of Solution Manager version 7.01.
    What is the process to upgrade the support pack to sp level 19? i have no exp to upgrade to EHP1 level..Any difference ?
    Thanks in advance
    Amar

    Hi Amarjit,
    Solution manager upgrade to EHP1 is same like other stack upgrade. You can do it using SAINT/JSPM. But only thing you need is good preparation.
    Check upgrade guide on http://service.sap.com/solutionmanager.
    Also, check SAP  Note 1276895 - Add. info. about Upgrading to SAP Solution Manager 7.0 EHP1 and SAP Note 1169247 - Enhancements to Solution Manager 7.0 EHP1 upgrade
    Thanks
    Sunny

  • How to integrate Solution Manager system to Enterprise Portal

    Hi all,
    HOW TO INTEGRATE SOLUTION MANAGER SYSTEM TO ENTERPRISE PORTAL SYSTEM

    Hi,
    First establish SSO between portal and solution manager.
    make the iview from com.sap.portal.epsolman.EPSolman
    check the link for help
    ep and solution manager support desk
    Thanks
    Santosh

  • Solution Manager Upgrade master media not found on download area

    Hi All,
    We have downloaded solution manager upgrade media from service marketplace. We are performing non-unicode upgrade.
    From the download area, we cannot find Upgrade master dvd or media. Media found are:
    51031485_1_SOLMAN4_UPGRADE
    51031485_2_SOLMAN4_UPGRADE
    Please advice.
    Many Thanks,
    Nischal

    I have managed to get prepare going.

  • Solution Manager upgrade issue on Linux

    Hi Alll,
    Need your inputs/thoughts on this issue.
    We are planning for Solution Manager upgrade from 3.1 to 4.0 and for this the setup and plan is as below:
    The production data of the solution manager has been copied as a VMX FILE(VM Player) file on to a test server and we have plans to upgrade that and check and then upgrade on the production system.
    The test machine has got a different IP address and hostname. From the test machine when I start the sap instance its affecting the Production machine and dueto which the production will not work until I stop the SAP Instance on the test machine.
    It cannot be a IP conflict or hostname conflict as we have them differently on the test machine. But still there is an issue. The IT dept says the issue is with the starting up of the instance and we dont know where to see what exactly is the problem.
    I am new to upgradation stuffs, this is my 1st assignment and I am not sure from where to start!!
    Can anyone of you tell me where to check for the details?
    SOLMAN is installed on a unix machine with oracle 9.2 and we are planning to upgrade it to SOLMAN 7.0
    any suggestions on where to look out for the possible issue?

    Hi,
    I did this a lot and know the side effects a little.
    My recipe:
    1. Start the copy without network and manage it from the VMWare Console. Change the IP address and make sure all references to the hostname (DNS and /etc/hosts) point to the new one. I hope you're working consistently with hostnames and no IP addresses.
    2. Configure the firewall (iptables) on the copied system to block all requests from and to the original production server. If there is any communication with other SAP servers (like monitoring agents, SLD, or others) block this too!
    3. Re-enable the network in VMWare.
    Alternatively: Can't you simply put this in a VLAN or a real seperated network with just the server and a management workstation?
    Hope that helps..
    Nikolaus

  • About Solution Manager upgrade from 3.1 to 4.0

    Hi colleague,
    I am in progress of finalizing a planning for an Upgrade project of Solution Manager from 3.1 to 4.0 release.
    The current usage of the Solution Manager usage is the following :
    - Only Blue Print and Implementation function used,
    - No modification (no repair),
    - Very few customizing : document type, key word,
    - More than 300 User : BRIDGE Program at Schneider Electric customer that uses Sol Man as implementation enabler and tool is very huge, with many SAP component - ECC, CRM, BW, SRM, EP, APO, XI ; + scope is all SE business organization worldwide,
    - We us Template approach (Template Project + Implementation Project per Roll Out),
    - DE/EN/FR installed and FR supplemented with EN,
    - Landscape is mapped,
    - We use Blue Print, business structure, few project administration function, IMG activities linked to Project/Structure, Dev objects linked to Project/Structure, documentation linked to Project/Structure, customizing distribution,
    - There are around 6000 documents stored in 2 used Project (one Template, other Implementation).
    Current plan is to perform 2 upgrade :
    - One on a SandBox Sol Man on which we will have before copied the Sol Man plateform used for project implementation task,
    - Another on the Sol Man plateform used (final).
    Strategy is in a first step to perform an upgrade without implementation of additional/new Sol Man functions (to see and qualify in a further phase) : iso functionality is the strategy.
    Now my concern / question.
    I did estimate roughly the upgrade duration and workload to 3 days (only for upgrade, not for preparation, pre-step, post-steps, validation, ...,
    I would like to know if such estimation is realistic, and if I have to check and pay attention to particular concern (I already collected all relevant SAP Note like 892412, 914910, 834534, ...).
    I expect to have after upgrade the same content, without any bad surprise.
    Thanks for your collaboration.
    Regards.
    Philippe Boyer SAP France (Project Management Team)

    Hi,
    I guess by now you would have started your upgrade. Sorry for the delay. That's a realistic/achievable estimate, goahead. Any specific queries about upgrade? feel free to revert back.
    --Ragu
    Downloading and installation of patches would consume more time.
    Message was edited by:
            Raguraman C

  • Install Solution Manager in RedHat Enterprise 6 with Oracle 11

    Hello ,
    In the marketplace-PAM,  RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
    Does anyone have any information on this subject?
    Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
    tks

    Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
    Note 1565179 - SAP software and Oracle Linux
    Thanks

  • Solution Manager Upgrade ST-PI and ST-A/PI

    System Details:
    SAP ERP 6.0 (BASIS 700) / SQL SERVER 2005
    Windows
    Hi
    We are planning to upgrade our ST-PI from  2005_1_700(0006) to      2008_1_700(0000) in our ERP System and BW System.
    Similarly we are also planning to upgrade ST-A/PI from 01K_ECC600 to 01L_ECC600.
    In the process, I am planning to upgrade SPAM/SAINT as well as R3Trans and tp.
    We are planning to implement this in
    01) ERP --> DEV, QAS, and PRD.
    02) BW --> DEV, QAS and PRD.
    Should we also upgrade our Solution manager system.  If so, how to find the prerequisities.
    Thanking you in anticipation
    Best Regards
    Raghunahth L

    Hi Uday,
    Thanks a lot for replying again.
    Infact, I had already gone throught the note 781448.
    But what really fishy is, using Solution Manager you have to do a lot of work like
    downloading latest patches, configuring EWA Alert etc and for everything you need to get connected with SAP Network.
    Since ST-A/PI is the core software which plays the communication part with SAP Network,
    and Solution Manager is the System playing the key role (as per SAP), but funny thing is
    that they have released the latest Patch for all systems except Solution Manager System.
    Even though it is being the fact, it is very hard to believe. Anyway thanks a lot for your time and your inputs were reassuring.
    Best regards,
    Raghunahth L

  • Solution Manager Upgrade Issue for "Business Process Monitoring"

    Hello,
    We had upgrade Solution Manager 7.1 SP08 to SP11.
    Earlier our BP Monitories were working fine which are not working now, also we are not able to use function “Load Monitor”.

    We are facing below major issues
    1. No system in Logical Component
    2. No RFC destination found
    3. Unable to load Monitors
    Also the BPMon configuration is not working post upgrade
    Kindly help us to resolve these issues.

  • Solution Manager Upgrade to SPS25

    Hello,
    We are preparing to upgrade our current installation of Solution Manager 7.0 to SPS25.  Is there anything we need to do with our existing maintenance and implementation projects prior to installing the upgrade? 
    Thank you for your recommendations.

    Hello Cynthia,
    Exactly what Release and SP Level is the system now?
    Usually upgrades are pretty seemless, its migrations that creates issues.
    What I would suggest is you go to http://service.sap.com/instguides
    Installation & Upgrade Guides >  SAP Components > SAP Solution Manager > Release 7.0 EHP 1
    Then click on #5 Upgrade Guides
    You will need to locate the upgrade guide for your OS/DB, and then you will have detailed information about the process.
    This should help a lot.
    Regards,
    Paul

  • Solution Manager upgrade

    Hello experts!, I'm doing an upgrade of my current Solution Manager (7.01 linux+db2) to solution Manager 7.1
    I created my maintenance transaction and downloaded upgrade files from SMP, but the SOLMANUP process is requesting to me the mount point containing "Export DVD for product CRM/SOLMAN", which one is that?
    Hope can you help me
    Thanks!

    Hi Sirkam,
    Besides downloading SP from MOPZ, you do need to download installation export, kernel and language DVD from SMP in order to upgrade solman.
    Do download the upgrade guide and media list from SMP for better understanding.
    Cheers,
    Nicholas Chang

  • Pre-Steps for Solution Manager Upgrade

    Hi Experts,
    We are currently planning to upgrade the Solution Manager system from SM7.01 SP25 to SM7.1 SP03.
    Can you please let me know the Pre-Steps that we need to consider in Solution Manager before Upgrading.
    Awaiting for your response.
    Regards,
    Satish Dhanalakoti

    Hi,
    In addtion to the experts' suggestions above, please also check:
    http://wiki.sdn.sap.com/wiki/display/SMSETUP/Home -> SolMan 7.1 Section.
    Could be of help.
    Regards,
    Srikishan

  • SOLUTION MANAGER UPGRADE - Error when shadow system Starting

    Hi All, We are upgrading our Solman system from 7.0 EHP 1 to SOLMAN 7.1. But the system is uable to start the Shadow
    system. *** ERROR => DpHdlDeadWp: W0 (pid 12046) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12046) exited with exit code 255 *** ERROR => DpHdlDeadWp: W4 (pid 12050) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12050) exited with exit code 255 DpMBufHwIdSet: set Hardware-ID ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296] MBUF state ACTIVE DpWpBlksLow: max wp blocks in queue is 800 (80 %) MBUF component UP DpMsgProcess: 1 server in MBUF DpAppcBlksLow: max appc blocks in queue is 500 (50 %) *** ERROR => DpHdlDeadWp: W3 (pid 12049) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12049) exited with exit code 255 Sun Jan 8 21:50:33 2012 *** ERROR => DpHdlDeadWp: W2 (pid 12048) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12048) exited with exit code 255 *** ERROR => DpHdlDeadWp: W5 (pid 12051) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12051) exited with exit code 255 *** ERROR => DpHdlDeadWp: W6 (pid 12052) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12052) exited with exit code 255 *** ERROR => DpHdlDeadWp: W7 (pid 12053) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12053) exited with exit code 255 *** ERROR => DpHdlDeadWp: W8 (pid 12054) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12054) exited with exit code 255 *** ERROR => DpHdlDeadWp: W9 (pid 12055) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12055) exited with exit code 255 *** ERROR => DpHdlDeadWp: W10 (pid 12056) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12056) exited with exit code 255 *** ERROR => DpHdlDeadWp: W11 (pid 12057) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12057) exited with exit code 255 kill(12045,0) -> ESRCH: process died DpStartStopMsg: send stop message (myname is >solmanqazone_KSQ_04 <) DpStartStopMsg: Write AD_STARTSTOP message with type= 0, name=solmanqazone_KSQ_04 , sapsysnr= 4, hostname=solmanqazone AdGetSelfIdentRecord: > < AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 60 AdCallRegisteredCvtToExt: opcode 60 call 102164870 AdCallRegisteredCvtToExt: opcode 60 exit rc=SAP_O_K AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 4 AdCallRegisteredCvtToExt: opcode 4 call 102160ff8 AdCallRegisteredCvtToExt: opcode 4 exit rc=SAP_O_K DpConvertRequest: net size = 189 bytes NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufSend starting NiIWrite: hdl 17 sent data (wrt=562,pac=1,MESG_IO) MsINiWrite: sent 562 bytes MsISnd2: send msg (ms hdr/msg 110/452 bytes) to name -, type 4, key - DpStartStopMsg: stop msg sent NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=274,pac=1,MESG_IO) NiBufIIn: NIBUF len=274 NiBufIIn: packet complete for hdl 17 NiBufSend starting NiIWrite: hdl 17 sent data (wrt=114,pac=1,MESG_IO) MsINiWrite: sent 114 bytes MsISnd2: send msg (ms hdr/msg 110/4 bytes) to name MSG_SERVER, type 0, key - MsSndName: MS_NOOP ok Send 4 bytes to MSG_SERVER NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=114,pac=1,MESG_IO) NiBufIIn: NIBUF len=114 NiBufIIn: packet complete for hdl 17 NiBufReceive starting MsINiRead: received 114 bytes MsIReceive: received msg (ms hdr/msg 110/4 bytes), flag 3, from MSG_SERVER , typ 0, key - Received 4 bytes from MSG_SERVER Received opcode MS_NOOP from msg_server, reply MSOP_OK MsOpReceive: ok MsISendKeepalive : keepalive sent to message server NiIRead: hdl 17 recv would block (errno=EAGAIN) Sun Jan 8 21:52:21 2012 NiIPeek: peek for hdl 17 timed out (r; 1000ms) NiIRead: read for hdl 17 timed out (1000ms) DpHalt: no more messages from the message server DpHalt: sync with message server o.k. DpHalt: detach from message server ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 12730] *** ERROR => e=28 semget(20465,1,2016) (28: No space left on device) [semux.c 498] *** ERROR => SemRq: Implicit SemInit failed. Key=65 [semux.c 1129] *** ERROR => Es2Cleanup: SemRq SEM_ES2_ADM (rc=1) [es2xx.c 1082] SemRq( 38, 1, -1) enter SemRq( 38, 1, -1) exit rtc=0, 0us SemRel( 38, 1 ) enter SemRel( 38, 1 ) exit rtc=0, 0us ShmDelete2( 73 ) DpHalt: cleanup event management DpHalt: cleanup shared memory/semaphores SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 7 ) = 0740 (octal) SemKeyPermission( 8 ) = 0740 (octal) SemKeyPermission( 10 ) = 0740 (octal) SemKeyPermission( 11 ) = 0740 (octal) SemKeyPermission( 12 ) = 0740 (octal) SemKeyPermission( 13 ) = 0740 (octal) SemKeyPermission( 14 ) = 0740 (octal) SemKeyPermission( 15 ) = 0740 (octal) SemKeyPermission( 16 ) = 0740 (octal) SemKeyPermission( 17 ) = 0740 (octal) SemKeyPermission( 18 ) = 0740 (octal) SemKeyPermission( 19 ) = 0740 (octal) SemKeyPermission( 20 ) = 0740 (octal) SemKeyPermission( 21 ) = 0740 (octal) SemKeyPermission( 22 ) = 0740 (octal) *** ERROR => e=28 semget(20422,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 24 ) = 0740 (octal) *** ERROR => e=28 semget(20424,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 25 ) = 0740 (octal) *** ERROR => e=28 semget(20425,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 26 ) = 0740 (octal) *** ERROR => e=28 semget(20426,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 27 ) = 0740 (octal) *** ERROR => e=28 semget(20427,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 28 ) = 0740 (octal) *** ERROR => e=28 semget(20428,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 29 ) = 0740 (octal) *** ERROR => e=28 semget(20429,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 30 ) = 0740 (octal) *** ERROR => e=28 semget(20430,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 31 ) = 0740 (octal) *** ERROR => e=28 semget(20431,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 35 ) = 0740 (octal) *** ERROR => e=28 semget(20435,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 42 ) = 0740 (octal) *** ERROR => e=28 semget(20442,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 43 ) = 0740 (octal) *** ERROR => e=28 semget(20443,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 44 ) = 0740 (octal) *** ERROR => e=28 semget(20444,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 45 ) = 0740 (octal) *** ERROR => e=28 semget(20445,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 47 ) = 0740 (octal) *** ERROR => e=28 semget(20447,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 48 ) = 0740 (octal) *** ERROR => e=28 semget(20448,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 49 ) = 0740 (octal) *** ERROR => e=28 semget(20449,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 50 ) = 0740 (octal) *** ERROR => e=28 semget(20450,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 51 ) = 0740 (octal) *** ERROR => e=28 semget(20451,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 53 ) = 0740 (octal) *** ERROR => e=28 semget(20453,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 54 ) = 0740 (octal) *** ERROR => e=28 semget(20454,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 55 ) = 0740 (octal) *** ERROR => e=28 semget(20455,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 56 ) = 0740 (octal) *** ERROR => e=28 semget(20456,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 57 ) = 0740 (octal) *** ERROR => e=28 semget(20457,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 58 ) = 0740 (octal) DpCleanupSharedResources: MpiCleanup ShmCleanup( 62 ) ShmCreate( 62, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 62, 3 ) ShmKeySharedMMU( 62 ) = 0 (octal) ShmProtect: shmat key 62 prot 3/0 done ShmCreate( 62, 0, 2, -> 0xfffffffe1d400000 ) MpiCleanup() -> MPI_OK DpCleanupSharedResources: removing Semaphore-Management DpCleanupSharedResources: removing request queue ShmCleanup( 31 ) ShmCreate( 31, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 31, 3 ) ShmKeySharedMMU( 31 ) = 0 (octal) ShmProtect: shmat key 31 prot 3/0 done ShmCreate( 31, 0, 2, -> 0xffffffff24000000 ) DpCleanupSharedResources: ShmCleanup SHM_SYS_ADM_KEY ShmCleanup( 1 ) ShmCreate( 1, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 1, 3 ) ShmKeySharedMMU( 1 ) = 0 (octal) ShmProtect: shmat key 1 prot 3/0 done ShmCreate( 1, 0, 2, -> 0xffffffff78100000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_ADM_KEY ShmCleanup( 2 ) ShmCreate( 2, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 2, 3 ) ShmKeySharedMMU( 2 ) = 0 (octal) ShmProtect: shmat key 2 prot 3/0 done ShmCreate( 2, 0, 2, -> 0xffffffff28800000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_CA_KEY ShmCleanup( 3 ) ShmCreate( 3, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 3, 3 ) ShmKeySharedMMU( 3 ) = 0 (octal) ShmProtect: shmat key 3 prot 3/0 done ShmCreate( 3, 0, 2, -> 0xffffffff24800000 ) DpCleanupSharedResources: ShmCleanup SHM_PF_KEY ShmCleanup( 4 ) ShmCreate( 4, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 4 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_SAPSCSA_AREA_KEY ShmCleanup( 5 ) ShmCreate( 5, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 5 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PXA_KEY ShmCleanup( 6 ) ShmCreate( 6, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 6 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_VB_ADM_KEY ShmCleanup( 7 ) ShmCreate( 7, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 7 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_AREA_KEY ShmCleanup( 8 ) ShmCreate( 8, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 8 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_ROLL_AREA_KEY ShmCleanup( 9 ) ShmCreate( 9, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 9 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_CALI_BUFFER ShmCleanup( 11 ) ShmCreate( 11, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 11, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_CCC_KEY ShmCleanup( 12 ) ShmCreate( 12, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 12, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_ALERT_AREA_KEY ShmCleanup( 13 ) ShmCreate( 13, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 13, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_PRES_BUF ShmCleanup( 14 ) ShmCreate( 14, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 14, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup DVS_SHM_KEY ShmCleanup( 15 ) ShmCreate( 15, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 15, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_SEM_MONI_BUFFER ShmCleanup( 16 ) ShmCreate( 16, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 16, 3 ) ShmCreate( 16, 0, 2, -> 0xffffffff29004000 ) ShmDelete2( 10 ) Sun Jan 8 21:52:22 2012 DpCleanupSharedResources: ShmCleanup SHM_ROLL_ADM_KEY ShmCleanup( 17 ) ShmCreate( 17, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 17, 0, 2, 0xffffffff7fffe9e0 ) ShmCreate( 10, 0, 2, 0xffffffff7fffe828 ) ShmKeyPermission( 10 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_ADM_KEY ShmCleanup( 18 ) ShmCreate( 18, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 18 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_TBUFF ShmCleanup( 19 ) ShmProtect( 52, 3 ) ShmKeySharedMMU( 52 ) = 0 (octal) ShmProtect: shmat key 52 prot 3/0 done ShmCreate( 52, 0, 2, -> 0xffffffff77600000 ) DpCleanupSharedResources: ShmCleanup SHM_ES_ADM_T ShmCleanup( 53 ) ShmCreate( 53, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 53 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_OBJ_BUFFER ShmCleanup( 54 ) ShmCreate( 54, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 54 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_RSPO_LOCAL_KEY ShmCleanup( 55 ) ShmCreate( 55, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 55 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PF_AS_KEY ShmCleanup( 56 ) ShmCreate( 56, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 56 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PROFILE ShmCleanup( 57 ) ShmCreate( 57, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 57, 3 ) ShmKeySharedMMU( 57 ) = 0 (octal) ShmProtect: shmat key 57 prot 3/0 done ShmCreate( 57, 0, 2, -> 0xffffffff75700000 ) DpCleanupSharedResources: ShmCleanup SHM_ENQID_KEY ShmCleanup( 58 )
    Regards, VIjay K.G

    Hi,
    From logs:
    28: No space left on device
    Check the disk space. If linux, use df -h command. Windows its easier
    Check if any drive / file system is 100% used up.
    Regards,
    Srikishan

  • Prerequisites for Solution Manager Upgradation

    Hi All,
             We are going to upgrade SolMan 7.0 to 7.1, what are the prerequisites to check ( Application Oriented not hardware oriented) i need to take care as SolMan Consultant. Could any one help regarding this as early as possible.
    Thanks & Regards,
    Krishnan Kumar.K

    Hello
    This involves lot of activities. Refer the market place.
    https://websmp204.sap-ag.de/instguides
    Thanks & regards
    bala

Maybe you are looking for